Skip site navigation (1) Skip section navigation (2)

Re: pg_dump locking info

From: Thom Brown <thom(at)linux(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: pg_dump locking info
Date: 2010-08-15 14:51:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
On 15 August 2010 15:38, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> 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
>>> , 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
>> should be
>> updated to make mention of streaming replication:
> But you can't use streaming replication for migration...

Hmm... yes, that's referring to migration to a new major version.
Ignore the streaming replication comment.

Thom Brown
Registered Linux user: #516935

In response to

pgsql-docs by date

Next:From: Tom LaneDate: 2010-08-15 19:47:19
Subject: Re: pgbench acronym tps
Previous:From: Scott MarloweDate: 2010-08-15 14:38:32
Subject: Re: pg_dump locking info

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group