From: Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
To: Thom Brown <thom@linux.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: pg_dump locking info
Date: Sun, 15 Aug 2010 11:45:13 +0200
Message-ID: <4C67B729.8010200@kaltenbrunner.cc> (raw)
In-Reply-To: <AANLkTi=B3x8MQQvd_xyncArJ9CLPT3cSu8-UjVNZVopr@mail.gmail.com>
References: <AANLkTi=B3x8MQQvd_xyncArJ9CLPT3cSu8-UjVNZVopr@mail.gmail.com>
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).
Stefan
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 using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: stefan@kaltenbrunner.cc, thom@linux.com
Subject: Re: pg_dump locking info
In-Reply-To: <4C67B729.8010200@kaltenbrunner.cc>
* 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