Re: pg_dump locking info - Mailing list pgsql-docs

From Thom Brown
Subject Re: pg_dump locking info
Date
Msg-id AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com
Whole thread Raw
In response to pg_dump locking info  (Thom Brown <thom@linux.com>)
Responses Re: pg_dump locking info  (Thom Brown <thom@linux.com>)
Re: pg_dump locking info  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-docs
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.

--
Thom Brown
Registered Linux user: #516935

pgsql-docs by date:

Previous
From: Thom Brown
Date:
Subject: pg_dump locking info
Next
From: Thom Brown
Date:
Subject: Re: pg_dump locking info