Re: Enhancement to pg_dump - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Enhancement to pg_dump
Date
Msg-id 8763mar6qp.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Enhancement to pg_dump  (Rob Kirkbride <rob.kirkbride@gmail.com>)
Responses Re: Enhancement to pg_dump
List pgsql-hackers
Rob Kirkbride <rob.kirkbride@gmail.com> writes:

> Richard,
>
> Yes, I've changed it use TRUNCATE rather than DELETE and it's working well for
> us now.

I'm a bit surprised actually as it sounded like you were aiming to avoid the
table lock. A TRUNCATE does require an exclusive lock on the table. It still
has advantages over DROP in that there is no window when the table does not
exist and any existing references to the table from views or functions will
continue to function.


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Visibility map, partial vacuums
Next
From: "Rob Kirkbride"
Date:
Subject: Re: Enhancement to pg_dump