Re: Avoid endless futile table locks in vacuuming.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid endless futile table locks in vacuuming.
Date: 2015-12-29 21:47:51
Message-ID: 4893.1451425671@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> If we are not doing a scan_all and we fail to acquire a clean-up lock on
> the last block, and the last block reports that it needs freezing, then we
> continue on to wait for the clean-up lock. But there is no need, we don't
> really need to freeze the block, and we already know whether it has tuples
> or not without the clean up lock. Couldn't we just set the flag based on
> hastup, then 'continue'?

Uh, isn't that what my patch is doing?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2015-12-30 00:08:00 Re: exposing pg_controldata and pg_config as functions
Previous Message Thomas Munro 2015-12-29 21:26:35 Re: Making tab-complete.c easier to maintain