pg_dump versioning

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_dump versioning
Date: 2005-10-03 01:06:01
Message-ID: 20051003010601.GG40138@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-10-03 01:46:07 Re: Inherited indexes.
Previous Message Andreas Pflug 2005-10-03 00:16:37 pgAdmin guru hints