Re: [PATCH] Unremovable tuple monitoring - Mailing list pgsql-hackers

From Royce Ausburn
Subject Re: [PATCH] Unremovable tuple monitoring
Date
Msg-id AD0D8D4E-F4AE-485D-9183-F2C4331BA15E@inomial.com
Whole thread Raw
In response to Re: [PATCH] Unremovable tuple monitoring  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Unremovable tuple monitoring
List pgsql-hackers
On 17/11/2011, at 1:47 AM, Robert Haas wrote:

> On Wed, Nov 16, 2011 at 9:34 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Robert Haas <robertmhaas@gmail.com> writes:
>>> Not sure about the log line, but allowing pgstattuple to distinguish
>>> between recently-dead and quite-thoroughly-dead seems useful.
>>
>> The dividing line is enormously unstable though.  pgstattuple's idea of
>> RecentGlobalXmin could even be significantly different from that of a
>> concurrently running VACUUM.  I can see the point of having VACUUM log
>> what it did, but opinions from the peanut gallery aren't worth much.
>
> Hmm, you have a point.
>
> But as Yeb points out, it seems like we should at least try to be more
> consistent about the terminology.


Thanks for the discussion so far all.  Would it be worthwhile to make another patch that addresses the points from
Yeb'sreviews?  It's not sounding like this unremovable tuple count is something that postgres wants, but I'm happy to
keepthe patch up to scratch if we're still not sure. 

Cheers,

--Royce



pgsql-hackers by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: psql + libedit command history truncation (was: psql history vs. dearmor (pgcrypto))
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Unremovable tuple monitoring