From: Marcin Kowalski <kowalski@datrix.co.za>
To: pgsql-admin@postgresql.org.pgsql-bugs
Subject: pg_dump potential bug
Date: Tue, 27 Mar 2001 11:03:07 +0200
Message-ID: <99pkvj$2are$1@news.tht.net> (raw)
Hi All...
I've got a slight problem with pg_dump in Postgres v7.0.3, in basically
duplicates all the data that it extracts
I do a
testdatabase>CREATE TABLE bob (number int4,description text);
testdatabase>INSERT INTO TABLE bob VALUES (4453,'This is just a test of
pg_dump');
then
kowalski@dagoba > pg_dump -t bob testdatabase
\connect - kowalski
CREATE TABLE "bob" (
"number" int4,
"description" text
);
CREATE TABLE "bob" (
"number" int4,
"description" text
);
COPY "bob" FROM stdin;
4453 This is just a test of pg_dump
\.
COPY "bob" FROM stdin;
4453 This is just a test of pg_dump
\.
As you can see the records are duplicated. I discovered this when I tried
to migrate from 7.0.3 to 7.1 and found performance suddenly took a terrible
dive. Is there a patch for pg_dump ??
Thanks for any help
MarCin
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-sql@postgresql.org
Cc: kowalski@datrix.co.za, pgsql-admin@postgresql.org.pgsql-bugs
Subject: Re: pg_dump potential bug
In-Reply-To: <99pkvj$2are$1@news.tht.net>
References: <99pkvj$2are$1@news.tht.net>
* 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