Re: pg_dump versioning - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_dump versioning
Date
Msg-id 200510030351.j933prd03166@candle.pha.pa.us
Whole thread Raw
In response to pg_dump versioning  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: pg_dump versioning
List pgsql-hackers
Jim C. Nasby wrote:
> Watching the discussion about how to handle nextval() and keep it dump
> compatible makes me wonder: would it be useful to encode database or
> dump version info into dumps? ISTM it would make it much more feasible
> to handle changes to how things work automatically.

Yes, we have talked about that, and it would work for pg_dump-generated
dumps.  What it might not work for cleanly are dumps moved a different
way, or application changes, so while it might help in some cases, being
able to get things working without the version info is desirable.

If we ever get to a case where we _need_ to use it, it would be good to
have, just in case.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: effective SELECT from child tables
Next
From: Tom Lane
Date:
Subject: Re: pg_dump versioning