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 20070912204403.GA6671@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?

I forgot to mention that I had patched this separately.  I back-patched
the removal of vacuum_delay all the way to 8.0, but the early release of
the AccessExclusive lock I limited to HEAD.



--
Alvaro Herrera                 http://www.amazon.com/gp/registry/DXLWNGRJD34J
"The West won the world not by the superiority of its ideas or values
or religion but rather by its superiority in applying organized violence.
Westerners often forget this fact, non-Westerners never do."
(Samuel P. Huntington)

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Make REINDEX DATABASE silently skip remote temp tables.
Next
From: adunstan@postgresql.org (Andrew Dunstan)
Date:
Subject: pgsql: Perform post-escaping encoding validity checks on SQL literals