From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: pg_dump locking info |
Date: | 2010-08-15 11:17:25 |
Message-ID: | AANLkTinMAQRC_Lom_WdF1E36H-xy9PZv2tuUDZKnD4Nj@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 15 August 2010 10:45, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> wrote:
> On 08/15/2010 11:01 AM, Thom Brown 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
>
> No it does not - it however blocks operations like ALTER TABLE while it is
> running(which is exactly how I read the above statement).
>
I'm not sure why I didn't read it that way now. :S My bad.
--
Thom Brown
Registered Linux user: #516935
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-08-15 11:18:50 | Re: pg_dump locking info |
Previous Message | Thom Brown | 2010-08-15 09:47:01 | Re: pg_dump locking info |