""Thomas Chille"" <thomas.chille@gmail.com> wrote
> Hi List,
>
> i run in to an error while dumping a db.
>
> after investigating it, i found a possible corrupted table. but i am not
sure.
> and i dont know how i can repair it? could it be a harddrive error?
>
>
> # now the error: SELECT * FROM hst_sales_report WHERE id = 5078867
>
> [6216 / 2006-06-19 18:46:23 CEST]LOG: 00000: connection received:
> host=[local] port=
> [6216 / 2006-06-19 18:46:23 CEST]LOCATION: BackendRun, postmaster.c:2679
> [6216 / 2006-06-19 18:46:23 CEST]LOG: 00000: connection authorized:
> user=postgres database=backoffice_db
> [6216 / 2006-06-19 18:46:23 CEST]LOCATION: BackendRun, postmaster.c:2751
> [6216 / 2006-06-19 18:46:23 CEST]LOG: 00000: statement: SELECT * FROM
> hst_sales_report WHERE id = 5078867
> [6216 / 2006-06-19 18:46:23 CEST]LOCATION: pg_parse_query, postgres.c:526
> [3762 / 2006-06-19 18:46:23 CEST]LOG: 00000: server process (PID
> 6216) was terminated by signal 11
> [3762 / 2006-06-19 18:46:23 CEST]LOCATION: LogChildExit,
postmaster.c:2358
> [3762 / 2006-06-19 18:46:23 CEST]LOG: 00000: terminating any other
> active server processes
> [3762 / 2006-06-19 18:46:23 CEST]LOCATION: HandleChildCrash,
postmaster.c:2251
> [3985 / 2006-06-19 18:46:23 CEST]WARNING: 57P02: terminating
> connection because of crash of another server process
> [3985 / 2006-06-19 18:46:23 CEST]DETAIL: The postmaster has commanded
> this server process to roll back the current transaction and exit,
> because another server process exited abnormally and possibly
> corrupted shared memory.
Which verison are you using? In any way, except a random hardware error, we
expect Postgres to be able to detect and report the problem instead of a
silent core dump. So can you gather the core dump and post it here?
Regards,
Qingqing