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

From Tom Lane
Subject Re: pgsql: Release the exclusive lock on the table early after truncating it
Date
Msg-id 1456.1189470306@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Release the exclusive lock on the table early after truncating it  (alvherre@postgresql.org (Alvaro Herrera))
Responses Re: pgsql: Release the exclusive lock on the table early after truncating it  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: pgsql: Release the exclusive lock on the table early after truncating it  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-committers
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.

            regards, tom lane

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Arrange for SET LOCAL's effects to persist until the end of the
Next
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Release the exclusive lock on the table early after truncating it