Re: Poorly thought out code in vacuum - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Poorly thought out code in vacuum
Date
Msg-id CA+TgmoYeYaZfa-oKqpu9Y=+vSdQf=kCcRxq-M30JPX4w+vkSpw@mail.gmail.com
Whole thread Raw
In response to Poorly thought out code in vacuum  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Poorly thought out code in vacuum  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Thu, Jan 5, 2012 at 7:37 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I suppose Robert had something more intelligent in mind than a tight
> loop when the buffer can't be exclusively locked, so maybe there is
> some other change that should be made here instead.

My intention was to skip the tuple, but I failed to notice the unusual
way in which this loop iterates.  How about something like the
attached?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.
Next
From: Simon Riggs
Date:
Subject: Re: Poorly thought out code in vacuum