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 4C0A5D1B55E for ; Tue, 2 Mar 2004 07:37:11 +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 52184-06 for ; Tue, 2 Mar 2004 03:36:59 -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 46ADBD1B50A for ; Tue, 2 Mar 2004 03:36:52 -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 i227ajdw030359; Tue, 2 Mar 2004 08:36:46 +0100 Message-ID: <4044398C.405@bitoek.uni-bayreuth.de> Date: Tue, 02 Mar 2004 08:36:44 +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 To: Tom Lane 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> <403C558B.3040502@bitoek.uni-bayreuth.de> <3259.1077720163@sss.pgh.pa.us> In-Reply-To: <3259.1077720163@sss.pgh.pa.us> 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: 200403/12 X-Sequence-Number: 12582 >>[ 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? > It's a RH7.1 with standard rpm kernel-2.4.2-2. The special thing is a proprietary infortrend kernel modul rd124f necessary to access a IFT-2101 raid. Unfortunately Infortrend does not supply a modul for a more recent linux distribution. The machine was originally intended to run Oracle on Windows... I will check whether the error occurs on an other machine with different kernel but identical database and postgres version. Regards, Stefan -- ----------------------------- Dr. Stefan Holzheu Tel.: 0921/55-5720 Fax.: 0921/55-5799 BITOeK Wiss. Sekretariat Universitaet Bayreuth D-95440 Bayreuth -----------------------------