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 BA78DD1E17E for ; Wed, 25 Feb 2004 14:43:21 +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 92334-01 for ; Wed, 25 Feb 2004 10:43:01 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 01CE8D1BAA5 for ; Wed, 25 Feb 2004 10:42:48 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1PEghNu003260; Wed, 25 Feb 2004 09:42:44 -0500 (EST) To: Stefan Holzheu Cc: ADMIN Subject: Re: Problems with pg_dump In-reply-to: <403C558B.3040502@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> <403C558B.3040502@bitoek.uni-bayreuth.de> Comments: In-reply-to Stefan Holzheu message dated "Wed, 25 Feb 2004 08:58:03 +0100" Date: Wed, 25 Feb 2004 09:42:43 -0500 Message-ID: <3259.1077720163@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/350 X-Sequence-Number: 12524 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