X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AD2063A3DC7 for ; Mon, 17 Jan 2005 20:34:23 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 57660-01 for ; Mon, 17 Jan 2005 20:34:18 +0000 (GMT) Received: from mail.dbasetek.com (dbasetek.com [66.134.187.210]) by svr1.postgresql.org (Postfix) with ESMTP id 5FCA13A3D32 for ; Mon, 17 Jan 2005 20:34:18 +0000 (GMT) Received: from [192.168.1.51] ([192.168.1.51]) by mail.dbasetek.com (8.12.11/8.12.11) with ESMTP id j0HKYHlQ017940; Mon, 17 Jan 2005 14:34:17 -0600 Message-ID: <41EC214B.4060206@dbasetek.com> Date: Mon, 17 Jan 2005 14:34:19 -0600 From: Robert D Oden User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: PgSQL ADMIN Subject: Re: closed connection unexpectedly References: <41EB9F98.5040008@dbasetek.com> <2102.1105977680@sss.pgh.pa.us> In-Reply-To: <2102.1105977680@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/179 X-Sequence-Number: 16038 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 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 > > >