From: Terry Schmitt <tschmitt@schmittworks.com>
To: pgsql-admin@postgresql.org
Subject: pg_dumpall blocking other sessions
Date: Thu, 30 Sep 2010 08:50:10 -0700
Message-ID: <AANLkTi=ztzVi4k1KkAMNLSNKjM7SP5tDBmvb1oPbfrMs@mail.gmail.com> (raw)
Hi All,
I had a situation where a session was getting blocked while per
performing a pg_dumpall.
I could see the pg_dumpall session executing a COPY command on a table
in one schema.
Another user session was attempting to truncate a different table in a
different schema, but in the same database. This session was being
blocked by the pg_dumpall session.
I intend to test this further, but my understanding was that pg_dump
was a non-blocking operation. I'm still on the learning curve with
Postgres 8.4 (actually EnterpriseDB Advanced Server), so maybe I just
need more detail on how pg_dumpall works.
Is the truncate perhaps the problem, but other dml is allowed?
Thanks much,
Terry
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-admin@postgresql.org
Cc: tschmitt@schmittworks.com
Subject: Re: pg_dumpall blocking other sessions
In-Reply-To: <AANLkTi=ztzVi4k1KkAMNLSNKjM7SP5tDBmvb1oPbfrMs@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