pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marcin Kowalski <kowalski@datrix.co.za>
To: pgsql-admin@postgresql.org
Subject: Re: pg_dump potential bug
Date: Wed, 28 Mar 2001 09:37:21 +0200
Message-ID: <99s4an$2s1i$1@news.tht.net> (raw)
References: <99pkvj$2are$1@news.tht.net>

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@datrix.co.za> writes:
> > 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
> > \.
>
> 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***
-----------------------------



view thread (4+ messages)  latest in thread

Message-ID: <99s4an$2s1i$1@news.tht.net>
Permalink:  ../99s4an$2s1i$1@news.tht.net/
Also on:    postgresql.org/message-id/99s4an$2s1i$1@news.tht.net

 · 

reply

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
  Subject: Re: pg_dump potential bug
  In-Reply-To: <99s4an$2s1i$1@news.tht.net>
  References: <99pkvj$2are$1@news.tht.net> <99s4an$2s1i$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