Обсуждение: closed connection unexpectedly

I am trying to execute the following SQL:

create table rdo_tmp0 as
select distinct *
from rp_na_mm
where acct_no like '1%'
and acct_no >= '13873365'

This is the result I get:

DBD::Pg::db do failed: server closed the connection unexpectedly

Postgres Log file:

Jan 17 05:06:51 dbs01 postgres[3130]: [8-1] LOG:  server process (PID
3332) was terminated by signal 11
Jan 17 05:06:51 dbs01 postgres[3130]: [9-1] LOG:  terminating any other
active server processes
Jan 17 05:06:51 dbs01 postgres[3321]: [12-1] WARNING:  terminating
connection because of crash of another server process
Jan 17 05:06:51 dbs01 postgres[3321]: [12-2] DETAIL:  The postmaster has
commanded this server process to roll back the current tran
saction and exit, because another server
Jan 17 05:06:51 dbs01 postgres[3331]: [8-1] WARNING:  terminating
connection because of crash of another server process
Jan 17 05:06:51 dbs01 postgres[3321]: [12-3]  process exited abnormally
and possibly corrupted shared memory.
Jan 17 05:06:51 dbs01 postgres[3321]: [12-4] HINT:  In a moment you
should be able to reconnect to the database and repeat your comm
and.
Jan 17 05:06:51 dbs01 postgres[3331]: [8-2] DETAIL:  The postmaster has
commanded this server process to roll back the current trans
action and exit, because another server
Jan 17 05:06:51 dbs01 postgres[3331]: [8-3]  process exited abnormally
and possibly corrupted shared memory.
Jan 17 05:06:51 dbs01 postgres[3331]: [8-4] HINT:  In a moment you
should be able to reconnect to the database and repeat your comma
nd.
Jan 17 05:06:51 dbs01 postgres[3130]: [10-1] LOG:  all server processes
terminated; reinitializing
Jan 17 05:06:51 dbs01 postgres[3333]: [11-1] LOG:  database system was
interrupted at 2005-01-17 05:05:31 CST
Jan 17 05:06:51 dbs01 postgres[3333]: [12-1] LOG:  checkpoint record is
at 215/F6D9DCDC
Jan 17 05:06:51 dbs01 postgres[3333]: [13-1] LOG:  redo record is at
215/F6D189BC; undo record is at 0/0; shutdown FALSE
Jan 17 05:06:51 dbs01 postgres[3333]: [14-1] LOG:  next transaction ID:
198072882; next OID: 514344047
Jan 17 05:06:51 dbs01 postgres[3333]: [15-1] LOG:  database system was
not properly shut down; automatic recovery in progress
Jan 17 05:06:51 dbs01 postgres[3333]: [16-1] LOG:  redo starts at
215/F6D189BC
Jan 17 05:06:52 dbs01 postgres[3333]: [17-1] LOG:  unexpected pageaddr
215/E0980000 in log file 533, segment 247, offset 9961472
Jan 17 05:06:52 dbs01 postgres[3333]: [18-1] LOG:  redo done at 215/F797FFBC
Jan 17 05:06:54 dbs01 postgres[3333]: [19-1] LOG:  database system is ready


Thanks in advance

Doug Oden

Robert D Oden <roden@dbasetek.com> writes:
> I am trying to execute the following SQL:
> create table rdo_tmp0 as
> select distinct *
> from rp_na_mm
> where acct_no like '1%'
> and acct_no >= '13873365'

> This is the result I get:

> DBD::Pg::db do failed: server closed the connection unexpectedly

Apparently you've got some corrupted data in the rp_na_mm table.
See the mail list archives concerning methods for tracking down
corrupted data.

            regards, tom lane

This table is a work table which can be rebuilt. I have tried dropping
this table and re-creating. I get the
same result  to the query. The log snippet I posted earlier reflects the
outcome after dropping and
re-creating. Wouldn't I eliminate corrupted data as an issue by dropping
and recreating or is it possible
for Postgres to use the same corrupted location when re-creating the table?

Doug


Tom Lane wrote:

>Robert D Oden <roden@dbasetek.com> writes:
>
>
>>I am trying to execute the following SQL:
>>create table rdo_tmp0 as
>>select distinct *
>>from rp_na_mm
>>where acct_no like '1%'
>>and acct_no >= '13873365'
>>
>>
>
>
>
>>This is the result I get:
>>
>>
>
>
>
>>DBD::Pg::db do failed: server closed the connection unexpectedly
>>
>>
>
>Apparently you've got some corrupted data in the rp_na_mm table.
>See the mail list archives concerning methods for tracking down
>corrupted data.
>
>            regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>

Robert D Oden <roden@dbasetek.com> writes:
> This table is a work table which can be rebuilt. I have tried dropping
> this table and re-creating. I get the
> same result  to the query.

Oh?  Can you provide a self-contained test case?  Also, what PG version
is this, on what platform?

            regards, tom lane