From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_dump locking info |
Date: | 2010-08-15 14:38:32 |
Message-ID: | AANLkTimbvQFaSR3=A9wRgSLm32iaUZygabzhLJ_disMP@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Sun, Aug 15, 2010 at 3:47 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 15 August 2010 10:38, Thom Brown <thom(at)linux(dot)com> wrote:
>>
>> Another thing I noticed, going back to
>> http://www.postgresql.org/docs/current/static/backup-file.html , is
>> that it makes no mention of the fact that file system level backups
>> are useless if being used to restore in a different major version.
>> Maybe "There are two restrictions, however, which make this method
>> impractical, or at least inferior to the pg_dump method" should be
>> changed to "There are three..." and add the point that
>> pg_dump/pg_dumpall is mostly immune to such limitations.
>>
>
> In the docs for version 9.0, I think the following from
> http://www.postgresql.org/docs/9.0/static/migration.html should be
> updated to make mention of streaming replication:
But you can't use streaming replication for migration...
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-15 14:51:18 | Re: pg_dump locking info |
Previous Message | Thom Brown | 2010-08-15 11:18:50 | Re: pg_dump locking info |