Re: pg_dump potential bug

Hi

I would have expected this problem to have been brought up long ago with
people doing database backups and restores. Anyway below are the details

I am running PostgreSQL v 7.0.3 (upgraded yesterday from 7.0.2) on SuSE 6.3
with 2.2.17(SMP) kernel with S/W raid patch.
The actual database is running on a 40 GIG Software RAID0 Ext2fs partition.
It has approximately 13million records in 9 tables with most of the data
residing in 2 tables(+- 6Mill Each). The machine is a Dual PII-350 with 256
meg of Ram. Each table has two indices, both on two fields.

Is it possible that one of the system tables has been corrupted and shows
multiple entries for the tables?? This makes me a bit worried about system
integrity. When I do a simple select * from tablename it works fine, what
does pg_dump do that I don't ???

Thanks in ADvance
MarCin

> Marcin Kowalski <kowalski(at)datrix(dot)co(dot)za> writes:
> > kowalski(at)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
> > \.
>
> Strange. I can't duplicate this (and neither can anyone else, or we'd
> have heard about it long since). What platform are you on? How did you
> build or obtain your executables?
>
> regards, tom lane

--
-----------------------------
Marcin Kowalski
Linux/Perl Developer
Datrix Solutions
Cel. 082-400-7603
***Open Source Kicks Ass***
-----------------------------