| 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> |
| Subject: | Re: Problems with pg_dump |
| Date: | 2004-02-25 14:42:43 |
| Message-ID: | 3259.1077720163@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phillip R. aka Qbert | 2004-02-25 15:49:58 | Linux (Debian Woody), psql: Can't delete or create databases |
| Previous Message | Stefan Holzheu | 2004-02-25 07:58:03 | Re: Problems with pg_dump |