Re: pg_dump: bug?

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump: bug?
Date: 2002-02-02 06:14:50
Message-ID: 3C5B83DA.5080408@pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> writes:
>
>>Now, is this a bug?
>>
>
> Good question. I don't think this is the only example of a
> non-self-consistent situation that could arise after a series of
> ALTER commands; I'm not sure that we can or should try to solve
> every one.

Ummm...at some point in time, PG will need to be able to dump and
recreate a database no matter what the history.

No matter whether or not "non-self-consistent situations" occur. PG
needs to be able to snapshot and restore current state, whether or not
it is a horror.

Or else you might as well state that, like MySQL, the only thing to do
is to knock down the database, tar files, and hope no one is interested
in 24x7 uptime.

When my clients ask about Oracle vs. PG I like to say "PG". They still
mostly say "Oracle" and I oblige.

--
Don Baccus
Portland, OR
http://donb.photo.net, http://birdnotes.net, http://openacs.org

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2002-02-02 11:27:00 Re: pg_dump: bug?
Previous Message Tom Lane 2002-02-02 05:29:34 Re: pg_dump: bug?