pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: scott <scott@QNET.COM>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: tgl@sss.pgh.pa.us
Cc: stefan.holzheu@bitoek.uni-bayreuth.de
Cc: pgsql-admin@postgresql.org
Subject: Re: Problems with pg_dump
Date: Wed, 25 Feb 2004 09:53:25 -0800
Message-ID: <000601c3fbc8$44d2c300$e2deddd1@scott> (raw)
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>

take my name and e-mail out of your address!!!! Wrong Scott!
----- Original Message ----- 
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Stefan Holzheu" <stefan.holzheu@bitoek.uni-bayreuth.de>
Cc: "ADMIN" <pgsql-admin@postgresql.org>
Sent: Wednesday, February 25, 2004 6:42 AM
Subject: Re: [ADMIN] Problems with pg_dump


> Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de> 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




view thread (11+ messages)  latest in thread

Message-ID: <000601c3fbc8$44d2c300$e2deddd1@scott>
Permalink:  ../000601c3fbc8$44d2c300$e2deddd1@scott/
Also on:    postgresql.org/message-id/000601c3fbc8$44d2c300$e2deddd1@scott

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: scott@QNET.COM, tgl@sss.pgh.pa.us, stefan.holzheu@bitoek.uni-bayreuth.de
  Subject: Re: Problems with pg_dump
  In-Reply-To: <000601c3fbc8$44d2c300$e2deddd1@scott>
  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> <000601c3fbc8$44d2c300$e2deddd1@scott>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox