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 B5B2BD1E11A for ; Wed, 25 Feb 2004 17:56:30 +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 68487-02 for ; Wed, 25 Feb 2004 13:56:27 -0400 (AST) Received: from mx-i.qnet.com (mx-i.qnet.com [209.221.198.23]) by svr1.postgresql.org (Postfix) with ESMTP id 26C8ED1E0DD for ; Wed, 25 Feb 2004 13:56:25 -0400 (AST) Received: from cello.qnet.com ([209.221.198.10]) by mx-i.qnet.com with esmtp (Exim 4.30) id 1Aw3Gg-000LRp-44; Wed, 25 Feb 2004 09:56:22 -0800 Received: from scott (arc0-pool222-226.dial.qnet.com [209.221.222.226]) by cello.qnet.com (8.9.3/8.9.1) with SMTP id JAA08627; Wed, 25 Feb 2004 09:56:16 -0800 (PST) Message-ID: <000601c3fbc8$44d2c300$e2deddd1@scott> From: "scott" To: "Tom Lane" Cc: , , 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> <403C558B.3040502@bitoek.uni-bayreuth.de> <3259.1077720163@sss.pgh.pa.us> Subject: Re: Problems with pg_dump Date: Wed, 25 Feb 2004 09:53:25 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/353 X-Sequence-Number: 12527 take my name and e-mail out of your address!!!! Wrong Scott! ----- Original Message ----- From: "Tom Lane" To: "Stefan Holzheu" Cc: "ADMIN" Sent: Wednesday, February 25, 2004 6:42 AM Subject: Re: [ADMIN] Problems with pg_dump > Stefan Holzheu writes: > > [ pg_dump shows data corruption over local socket but not TCP ] > > That is really odd. > > > 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? > > No, not that I know of. You could modify libpq to dump everything it > receives from the socket to a log file, and then compare the results > from local socket and TCP cases. > > The whole thing is bizarre though. AFAICS it must represent a kernel > bug. What is your platform exactly? > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org