pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thom Brown <thom@linux.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: pg_dump locking info
Date: Sun, 15 Aug 2010 10:38:03 +0100
Message-ID: <AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com>
References: <AANLkTi=B3x8MQQvd_xyncArJ9CLPT3cSu8-UjVNZVopr@mail.gmail.com>
	<AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com>

On 15 August 2010 10:29, Thom Brown <thom@linux.com> wrote:
> On 15 August 2010 10:01, Thom Brown <thom@linux.com> wrote:
>> Is this right?  I'm looking at
>> http://www.postgresql.org/docs/current/static/backup-dump.html
>>
>> It says, "pg_dump does not block other operations on the database
>> while it is working. (Exceptions are those operations that need to
>> operate with an exclusive lock, such as most forms of ALTER TABLE.)"
>>
>> So pg_dump actually performs an ALTER TABLE sometimes? :S
>>
>
> And whilst I was perusing the docs, I also noticed this on
> http://www.postgresql.org/docs/current/static/backup.html
>
> "Each has its own strengths and weaknesses. Each is discussed in turn below."
>
> That sentence is at the bottom of the page.  It would make sense in a
> PDF, but might be a confusing in section-by-section HTML
> documentation.
>

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.

-- 
Thom Brown
Registered Linux user: #516935



view thread (15+ messages)  latest in thread

Message-ID: <AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com>
Permalink:  ../AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com/
Also on:    postgresql.org/message-id/AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: thom@linux.com
  Subject: Re: pg_dump locking info
  In-Reply-To: <AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com>
  References: <AANLkTi=B3x8MQQvd_xyncArJ9CLPT3cSu8-UjVNZVopr@mail.gmail.com> <AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com> <AANLkTikoALbeega4O1s70u_5x62Ku2P9txCo+o7-fMRR@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox