X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 507CB9DC81E for ; Mon, 2 Jan 2006 16:32:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 89820-10 for ; Mon, 2 Jan 2006 16:32:11 -0400 (AST) X-Greylist: delayed 01:26:36.6956 by SQLgrey- Received: from exchange.meridiascapital.com (exchange.meridiascapital.com [65.90.55.78]) by postgresql.org (Postfix) with ESMTP id 2F9BC9DC80F for ; Mon, 2 Jan 2006 16:32:07 -0400 (AST) Received: from 192.168.19.129 ([192.168.19.129]) by atherton-ex-01.meridias.local ([192.168.8.78]) with Microsoft Exchange Server HTTP-DAV ; Mon, 2 Jan 2006 20:32:08 +0000 Received: from sharp by ATHERTON-EX-01; 02 Jan 2006 13:32:08 -0700 Subject: Re: Emergency - Need assistance From: warren little To: Tom Lane Cc: pgsql-admin@postgresql.org In-Reply-To: <11864.1136232604@sss.pgh.pa.us> References: <1136228730.16094.12.camel@sharp> <11864.1136232604@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 02 Jan 2006 13:32:08 -0700 Message-Id: <1136233928.16094.33.camel@sharp> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 (2.2.2-5) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.121 required=5 tests=[AWL=0.120, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 0.121 X-Spam-Level: X-Archive-Number: 200601/18 X-Sequence-Number: 20106 Tom, The extent of the messages I received from the command pg_dump -Fc --table=casedocument -d tigrissave | pg_restore --verbose -d tigris is listed below: pg_dump: SQL command failed pg_dump: Error message from server: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor pg_restore: [custom archiver] could not read data block -- expected 1, got 0 pg_restore: *** aborted because of error I had removed all the files in pg_log prior to getting this error and no new logfile was created. I'm guessing I screwed up the logger when removing all the files, but I assumed that when writing to the error logs the backend would create a file if one did not exist. I currently attempt to run the dump/restore with the zero_damaged_pages turned on to see if the results yield something more useful. About the beta version, this is temporary, hadn't really planned on running production on our development box. Haven't had any issues with 8.1beta for a few months and will be moving to 8.1.x as soon as some new hardware arrives (about a week). thanks On Mon, 2006-01-02 at 15:10 -0500, Tom Lane wrote: > warren little writes: > > I received the following error message when trying to copy a table from > > one database to another on the same cluster: > > > pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor > > pg_restore: [custom archiver] could not read data block -- expected 1, > > got 0 > > pg_restore: *** aborted because of error > > You seem to have omitted the messages that would indicate what's > actually wrong; the above is all just subsidiary damage after whatever > caused the FETCH to fail. > > > The table is about 25GB in size and takes a long time to dump/restore > > and I'm running out of time to get the cluster back into production. > > > note running: > > PostgreSQL 8.1beta4 on x86_64-unknown-linux-gnu, compiled by GCC gcc > > (GCC) 3.4.4 20050721 (Red Hat 3.4.4-2)" > > You're running a production database on a beta release?? > > regards, tom lane -- Warren Little CTO Meridias Capital Inc ph 866.369.7763