Re: closed connection unexpectedly

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
>
>
>