Horton

Re: Hot Standby btree delete records and vacuum_defer_cleanup_age

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

View thread
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers@postgresql.org, Noah Misch <noah@leadboat.com>
Date: 2011-03-11T07:46:10Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Reduce spurious Hot Standby conflicts from never-visible records.

On 11.03.2011 06:21, Fujii Masao wrote:
> On Thu, Dec 9, 2010 at 4:55 PM, Simon Riggs<simon@2ndquadrant.com>  wrote:
>> On Thu, 2010-12-09 at 00:16 +0100, Heikki Linnakangas wrote:
>>> On 09.12.2010 00:10, Heikki Linnakangas wrote:
>>>> On 08.12.2010 16:00, Simon Riggs wrote:
>>>>> Heikki pointed out to me that the btree delete record processing does
>>>>> not respect vacuum_defer_cleanup_age. It should.
>>>>>
>>>>> Attached patch to implement that.
>>>>>
>>>>> Looking to commit in next few hours barring objections/suggestions, to
>>>>> both HEAD and 9_0_STABLE, in time for next minor release.
>>>>
>>>> Please note that it was Noah Misch that raised this a while ago:
>>>>
>>>> http://archives.postgresql.org/pgsql-hackers/2010-11/msg01919.php
>>>
>>> On closer look, that's not actually the same issue, sorry for the noise..
>>
>> Heikki, this one *is* important. Will fix. Thanks for the analysis Noah.
>
> Is this an open item for 9.1?

Simon fixed it, commit b9075a6d2f9b07a00262a670dd60272904c79dce.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com