X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5F4C9D1B447 for ; Mon, 26 Jan 2004 19:30:09 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 92297-05 for ; Mon, 26 Jan 2004 15:29:39 -0400 (AST) Received: from bitoek.uni-bayreuth.de (bti0x1.bitoek.uni-bayreuth.de [132.180.112.2]) by svr1.postgresql.org (Postfix) with ESMTP id C2B9DD1B45B for ; Mon, 26 Jan 2004 15:29:36 -0400 (AST) Received: from bitoek.uni-bayreuth.de (bti0x027.bitoek.uni-bayreuth.de [132.180.112.27]) by bitoek.uni-bayreuth.de (8.12.7/8.12.7) with ESMTP id i0QJTYYm003993; Mon, 26 Jan 2004 20:29:34 +0100 Message-ID: <40156A9D.5040302@bitoek.uni-bayreuth.de> Date: Mon, 26 Jan 2004 20:29:33 +0100 From: Stefan Holzheu User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.4) Gecko/20030624 X-Accept-Language: de-at, de, en-us, en MIME-Version: 1.0 To: Tom Lane Cc: ADMIN Subject: Re: Problems with pg_dump References: <40150D23.8000903@bitoek.uni-bayreuth.de> <7276.1075127998@sss.pgh.pa.us> <401532C0.5010402@bitoek.uni-bayreuth.de> <7946.1075133986@sss.pgh.pa.us> In-Reply-To: <7946.1075133986@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS - amavis-milter (http://www.amavis.org/) X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/243 X-Sequence-Number: 12106 > >>pg_dump: lost synchronization with server: got message type "5", length >>842281016 > > >>The error does not occur always and not always with the same table. > > > Oh, that's even more interesting. Is the failure message itself > consistent --- that is, is it always complaining about "message type 5" > and the same bizarre length value? The "length" looks like it's really > ASCII text ("2408" to be specific), so somehow libpq is misinterpreting > a piece of the COPY datastream as the start of a new message. > The failure looks similarly but the number do not exactly the same: pg_dump: lost synchronization with server: got message type "4", length 858863113 pg_dump: SQL command to dump the contents of table "aggr_max_hour" failed: PQendcopy() failed. pg_dump: Error message from server: lost synchronization with server: got message type "4", length 858863113 pg_dump: The command was: COPY messungen.aggr_max_hour (id, von, wert, counts) TO stdout; > >>However, the error occurs only on that kind of aggregation tables. There >>is a cron-job keeping the tables up to date, starting all 10 minutes. >>The job does delete and inserts on the table. Could this somehow block >>the dump process? Normally it should not? > > > It's hard to see how another backend would have anything to do with > this, unless perhaps the error is dependent on a particular data value > that is sometimes present in the table and sometimes not. It looks to > me like either libpq or the backend is miscounting the number of data > bytes in the COPY datastream. Would it be possible for you to use a > packet sniffer to capture the communication between pg_dump and the > backend? If we could look at exactly what's going over the wire, it > would help to pin down the blame. > Well, I never used a packet sniffer but if anyone tells me what to capture, I'd be glad to. PostgreSQL is really a great piece of software, keep on making it even better! Stefan -- ----------------------------- Dr. Stefan Holzheu Tel.: 0921/55-5720 Fax.: 0921/55-5799 BITOeK Wiss. Sekretariat Universitaet Bayreuth D-95440 Bayreuth -----------------------------