From: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Release notes for upgrading |
Date: | 2004-08-17 00:43:24 |
Message-ID: | 20040816214313.Y55723@ganymede.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 11 Aug 2004, Robert Treat wrote:
> On Wed, 2004-08-11 at 01:11, Tom Lane wrote:
>> Robert Treat <xzilla(at)users(dot)sourceforge(dot)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?
Exact text you'd like to have added?
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
From | Date | Subject | |
---|---|---|---|
Next Message | CSN | 2004-08-17 04:33:03 | Re: COPY with column headings |
Previous Message | Sailesh Krishnamurthy | 2004-08-17 00:28:07 | Re: pulling projection up in plans |