Re: pgsql: Release the exclusive lock on the table early after truncating it - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Release the exclusive lock on the table early after truncating it
Date
Msg-id 20070911002641.GF3060@alvh.no-ip.org
Whole thread Raw
In response to Re: pgsql: Release the exclusive lock on the table early after truncating it  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane wrote:
> alvherre@postgresql.org (Alvaro Herrera) writes:
> > Release the exclusive lock on the table early after truncating it in lazy
> > vacuum, instead of waiting till commit.
>
> Weren't you going to disable vacuum_delay in that stretch of code, too?
>
> BTW, not sure if you realized this, but just deleting the
> vacuum_delay_point call is probably a bad idea --- replace it
> with CHECK_FOR_INTERRUPTS() instead.

Hmm, I didn't.  Will fix.

Actually, now that you mention it, I remember that Alexey Kluykin (a
colleague from Command Prompt) had already mentioned it to me and I
forgot :-(

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Release the exclusive lock on the table early after truncating it
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Rename recently-added pg_stat_activity column from txn_start to