X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 45FA2D1BAA6 for ; Wed, 25 Feb 2004 07:58:10 +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 64607-02 for ; Wed, 25 Feb 2004 03:58:09 -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 6190ED1BAA3 for ; Wed, 25 Feb 2004 03:58:06 -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 i1P7w5dw018103 for ; Wed, 25 Feb 2004 08:58:05 +0100 Message-ID: <403C558B.3040502@bitoek.uni-bayreuth.de> Date: Wed, 25 Feb 2004 08:58:03 +0100 From: Stefan Holzheu User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6) Gecko/20040113 X-Accept-Language: de-at, de, en-us, en MIME-Version: 1.0 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> <40156A9D.5040302@bitoek.uni-bayreuth.de> In-Reply-To: <40156A9D.5040302@bitoek.uni-bayreuth.de> 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: 200402/349 X-Sequence-Number: 12523 > > 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. > In order to capture the pg_dump traffic with tcpdump we changed the pg_dump command from pg_dump DB > ... to pg_dump -h 127.0.0.2 DB > ... Since that time the dump completed without any errors. Before using local connection pg_dump failed to about 50%. Anyway, we can live with that solution. But still I'd be curious to know what is the problem with local connections. Is there a way to capture traffic of local socket connections? Stefan -- ----------------------------- Dr. Stefan Holzheu Tel.: 0921/55-5720 Fax.: 0921/55-5799 BITOeK Wiss. Sekretariat Universitaet Bayreuth D-95440 Bayreuth -----------------------------