Re: pgsql: Release the exclusive lock on the table early after truncating it

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Release the exclusive lock on the table early after truncating it
Date: 2007-09-11 00:25:06
Message-ID: 1456.1189470306@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

alvherre(at)postgresql(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2007-09-11 00:26:41 Re: pgsql: Release the exclusive lock on the table early after truncating it
Previous Message Tom Lane 2007-09-11 00:06:42 pgsql: Arrange for SET LOCAL's effects to persist until the end of the