From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de>
Cc: ADMIN <pgsql-admin@postgresql.org>
Subject: Re: Problems with pg_dump
Date: Mon, 26 Jan 2004 17:48:35 -0500
Message-ID: <23709.1075157315@sss.pgh.pa.us> (raw)
In-Reply-To: <40156A9D.5040302@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>
Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de> writes:
> Well, I never used a packet sniffer but if anyone tells me what to
> capture, I'd be glad to.
Since we don't know where exactly in the table the error occurs, I think
you'll just have to capture the whole connection traffic between pg_dump
and the backend. You could help keep it to a reasonable size by doing a
selective dump of just one table, viz "pg_dump -t tablename dbname",
although I guess you might have to try a few times to reproduce the
error that way ...
regards, tom lane
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: tgl@sss.pgh.pa.us, stefan.holzheu@bitoek.uni-bayreuth.de
Subject: Re: Problems with pg_dump
In-Reply-To: <23709.1075157315@sss.pgh.pa.us>
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> <23709.1075157315@sss.pgh.pa.us>
* 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