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 954FBD1D202 for ; Mon, 26 Jan 2004 16:24:24 +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 31948-06 for ; Mon, 26 Jan 2004 12:23:53 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 82DCAD1D2E3 for ; Mon, 26 Jan 2004 12:20:05 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0QGJknX007947; Mon, 26 Jan 2004 11:19:46 -0500 (EST) To: Stefan Holzheu Cc: ADMIN Subject: Re: Problems with pg_dump In-reply-to: <401532C0.5010402@bitoek.uni-bayreuth.de> References: <40150D23.8000903@bitoek.uni-bayreuth.de> <7276.1075127998@sss.pgh.pa.us> <401532C0.5010402@bitoek.uni-bayreuth.de> Comments: In-reply-to Stefan Holzheu message dated "Mon, 26 Jan 2004 16:31:12 +0100" Date: Mon, 26 Jan 2004 11:19:46 -0500 Message-ID: <7946.1075133986@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/232 X-Sequence-Number: 12095 Stefan Holzheu writes: > 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. > 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. regards, tom lane