BUG #6167: pg_dump fails on table lock

From: "Jesper Engman" <jesper(at)engman(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6167: pg_dump fails on table lock
Date: 2011-08-18 01:05:31
Message-ID: 201108180105.p7I15VEk025312@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

The following bug has been logged online:

Bug reference: 6167
Logged by: Jesper Engman
Email address: jesper(at)engman(dot)net
PostgreSQL version: 8.3.10
Operating system: Linux
Description: pg_dump fails on table lock

I have tables that exists for short time periods, sometimes for as short as
5 min. pg_dump is starting to fail due to a problem to lock these tables:

pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: relation
"vehicle_change_partitions.vehicle_change_export_p4368494" does not exist
pg_dump: The command was: LOCK TABLE
vehicle_change_partitions.vehicle_change_export_p4368494 IN ACCESS SHARE
Backup failed: PGPASSWORD=xxxxx && export PGPASSWORD && export PGOPTIONS="-c
statement_timeout=0 -c maintenance_work_mem=2147483647" && /usr/bin/pg_dump
-h xxx.xxx.xxx.xxx -U postgres --ignore-version -Fc -Z 6 xxxxxxxx >
Account: xxxxxxxx Backup failed

How is this possible - pg_dump is a serializable transaction? It doesn't
seem to be tripped up by some other backend function since this actually
fails on the lock.


Browse pgsql-bugs by date

  From Date Subject
Next Message Simon Riggs 2011-08-18 11:03:04 Re: BUG #6167: pg_dump fails on table lock
Previous Message Tom Lane 2011-08-17 23:32:31 Re: BUG #6166: configure from source fails with 'This platform is not thread-safe.' but was actually /tmp perms