Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to
Date: 2010-01-31 19:48:25
Message-ID: 4B65DE89.3040000@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs wrote:
> On Sun, 2010-01-31 at 14:07 -0500, Tom Lane wrote:
>
>>> The commit is a one line change, with parameter to control it, discussed
>>> by Heikki and myself in December 2008. I stand by the accuracy of the
>>> change; the parameter is really to ensure we can test during beta.
>> Well, I was waiting to see if anyone else had an opinion, but: my
>> opinion is that a GUC is not appropriate here. Either test it yourself
>> enough to be sure it's a win, or don't put it in.
>
> I will remove the parameter then, keeping the augmentation. That OK?

Well how much is the actual hit with this on the master for different
workloads do we have realistic numbers on that? Also how much of an
actual win is it in the other direction - as in under what circumstances
and workloads does it help in avoiding superflous cancelations on the
standby?

Stefan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2010-01-31 20:13:55 Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to
Previous Message Simon Riggs 2010-01-31 19:42:55 Re: Re: [COMMITTERS] pgsql: Augment WAL records for btree delete with GetOldestXmin() to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-01-31 19:49:25 Re: Hot Standby and VACUUM FULL
Previous Message Dimitri Fontaine 2010-01-31 19:48:19 Re: development setup and libdir