From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_dump locking info |
Date: | 2010-08-15 09:29:39 |
Message-ID: | AANLkTimfssadCt+9w9-iqHpbcKYm8=yH5vYGAJDsW2TA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 15 August 2010 10:01, Thom Brown <thom(at)linux(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-15 09:38:03 | Re: pg_dump locking info |
Previous Message | Thom Brown | 2010-08-15 09:01:18 | pg_dump locking info |