Re: mistakes in postgresql-snapshots (7.3) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: mistakes in postgresql-snapshots (7.3)
Date
Msg-id 5170.1029303198@sss.pgh.pa.us
Whole thread Raw
In response to Re: mistakes in postgresql-snapshots (7.3)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: mistakes in postgresql-snapshots (7.3)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: mistakes in postgresql-snapshots (7.3)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Is this something we need to address for 7.3?

Peter pointed out that he'd already hacked pg_dump to do the right
thing (or at least what is arguably the right thing) against older
databases.  That covers LANGUAGE, FUNCTION, and other objects-within-
a-database cases.  pg_dumpall doesn't yet do the right thing at the
database level, but I believe he's planning to take care of that.

A larger problem is that this only works if you use 7.3 pg_dump
to dump your older database.  If you dump with your then-current
pg_dump, you'll be unhappy with the permissions that result after
reloading into your new 7.3 server.

I'm not sure there is anything we can do about this without making
life worse.  But it's annoying.  Any thoughts?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: mistakes in postgresql-snapshots (7.3)
Next
From: Bruce Momjian
Date:
Subject: Re: Bug #737: PQescapeBytea parameter #3 size_t *to_length