| From: | Robert Haas <robertmhaas(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 20:58:39 |
| Message-ID: | AANLkTinGe6Pzg-L1=8wDpZxC4ZTD_SHZ9e4nRXr8qD=D@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sun, Aug 15, 2010 at 5:38 AM, 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.
Probably we need to say something a bit more nuanced than that, as
there can certainly be wrinkles in that area.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-15 21:01:30 | Re: pg_dump locking info |
| Previous Message | Robert Haas | 2010-08-15 20:56:43 | Re: pg_dump locking info |