Skip site navigation (1) Skip section navigation (2)

Re: Problems with pg_dump

From: "scott" <scott(at)QNET(dot)COM>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)de>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Problems with pg_dump
Date: 2004-02-25 17:53:25
Message-ID: 000601c3fbc8$44d2c300$e2deddd1@scott (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
take my name and e-mail out of your address!!!! Wrong Scott!
----- Original Message ----- 
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stefan Holzheu" <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)de>
Cc: "ADMIN" <pgsql-admin(at)postgresql(dot)org>
Sent: Wednesday, February 25, 2004 6:42 AM
Subject: Re: [ADMIN] Problems with pg_dump

> Stefan Holzheu <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)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?

In response to

pgsql-admin by date

Next:From: karthikeyanDate: 2004-02-26 03:56:47
Subject: unsubscribe
Previous:From: Phillip R. aka QbertDate: 2004-02-25 17:18:41
Subject: Re: Linux (Debian Woody), psql: Can't delete or create databases

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group