pg_dump versioning - Mailing list pgsql-hackers

From Jim C. Nasby
Subject pg_dump versioning
Date
Msg-id 20051003010601.GG40138@pervasive.com
Whole thread Raw
Responses Re: pg_dump versioning
List pgsql-hackers
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.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: pgAdmin guru hints
Next
From: Tom Lane
Date:
Subject: Re: Inherited indexes.