Release notes for upgrading
Can we put in a recommendation in the release notes that people use 8.0
pg_dump to do their dump? I think that will make everyone's upgrades go
much more smoothly, and we will get many fewer complaints.
I don't think many users realise they can use the next version's pg_dump
to upgrade. I think it should be put in every release notes!
Chris
On Tuesday 10 August 2004 22:57, Christopher Kings-Lynne wrote:
Can we put in a recommendation in the release notes that people use 8.0
pg_dump to do their dump? I think that will make everyone's upgrades go
much more smoothly, and we will get many fewer complaints.I don't think many users realise they can use the next version's pg_dump
to upgrade. I think it should be put in every release notes!
Assuming we're not ready to recommend Slony for upgrades, I would second this
idea based on my experience of several cases where I *had* to dump a database
using the newer pg_dump to get it to upgrade reliably. In fact I just came
across a 7.3 database that no longer works with standard -Fc backups since
the schema cannot be reloaded...
--
Robert Treat
Build A Better Lamp :: Linux Apache {middleware} PostgreSQL
Robert Treat <xzilla@users.sourceforge.net> writes:
On Tuesday 10 August 2004 22:57, Christopher Kings-Lynne wrote:
I don't think many users realise they can use the next version's pg_dump
to upgrade. I think it should be put in every release notes!
Assuming we're not ready to recommend Slony for upgrades, I would second this
idea based on my experience of several cases where I *had* to dump a database
using the newer pg_dump to get it to upgrade reliably.
This has been standard lore for awhile. Where should we document it
exactly?
regards, tom lane
On Wed, 2004-08-11 at 01:11, Tom Lane wrote:
Robert Treat <xzilla@users.sourceforge.net> writes:
On Tuesday 10 August 2004 22:57, Christopher Kings-Lynne wrote:
I don't think many users realise they can use the next version's pg_dump
to upgrade. I think it should be put in every release notes!Assuming we're not ready to recommend Slony for upgrades, I would second this
idea based on my experience of several cases where I *had* to dump a database
using the newer pg_dump to get it to upgrade reliably.This has been standard lore for awhile. Where should we document it
exactly?
Actually it seems it is already mentioned in
http://developer.postgresql.org/docs/postgres/install-upgrading.html and
somewhat inferred in
http://developer.postgresql.org/docs/postgres/migration.html
I'll take a swing at making the language a little stronger. We could
also add it as a mailing list hint. Chris, you have any other ideas
where you would like to see it?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
I'll take a swing at making the language a little stronger. We could
also add it as a mailing list hint. Chris, you have any other ideas
where you would like to see it?
Literally in the release notes - that's all that anyone reads of a new
release :) Wherever it says 'upgrading to 8.0 requires a full dump and
reload'.
Chris
On Wed, 11 Aug 2004, Robert Treat wrote:
On Wed, 2004-08-11 at 01:11, Tom Lane wrote:
Robert Treat <xzilla@users.sourceforge.net> writes:
On Tuesday 10 August 2004 22:57, Christopher Kings-Lynne wrote:
I don't think many users realise they can use the next version's pg_dump
to upgrade. I think it should be put in every release notes!Assuming we're not ready to recommend Slony for upgrades, I would second this
idea based on my experience of several cases where I *had* to dump a database
using the newer pg_dump to get it to upgrade reliably.This has been standard lore for awhile. Where should we document it
exactly?Actually it seems it is already mentioned in
http://developer.postgresql.org/docs/postgres/install-upgrading.html and
somewhat inferred in
http://developer.postgresql.org/docs/postgres/migration.htmlI'll take a swing at making the language a little stronger. We could
also add it as a mailing list hint. Chris, you have any other ideas
where you would like to see it?
Exact text you'd like to have added?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664