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 A91EFD1E151 for ; Mon, 26 Jan 2004 22:49:07 +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 67372-07 for ; Mon, 26 Jan 2004 18:48:38 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9758DD1DD3B for ; Mon, 26 Jan 2004 18:48:35 -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 i0QMmanX023710; Mon, 26 Jan 2004 17:48:36 -0500 (EST) To: Stefan Holzheu Cc: ADMIN Subject: Re: Problems with pg_dump In-reply-to: <40156A9D.5040302@bitoek.uni-bayreuth.de> 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> Comments: In-reply-to Stefan Holzheu message dated "Mon, 26 Jan 2004 20:29:33 +0100" Date: Mon, 26 Jan 2004 17:48:35 -0500 Message-ID: <23709.1075157315@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/245 X-Sequence-Number: 12108 Stefan Holzheu writes: > Well, I never used a packet sniffer but if anyone tells me what to > capture, I'd be glad to. Since we don't know where exactly in the table the error occurs, I think you'll just have to capture the whole connection traffic between pg_dump and the backend. You could help keep it to a reasonable size by doing a selective dump of just one table, viz "pg_dump -t tablename dbname", although I guess you might have to try a few times to reproduce the error that way ... regards, tom lane