From: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: [PATCH] Unremovable tuple monitoring |
Date: | 2011-11-17 22:49:45 |
Message-ID: | AD0D8D4E-F4AE-485D-9183-F2C4331BA15E@inomial.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)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's reviews? It's not sounding like this unremovable tuple count is something that postgres wants, but I'm happy to keep the patch up to scratch if we're still not sure.
Cheers,
--Royce
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-11-17 23:44:34 | Re: [PATCH] Unremovable tuple monitoring |
Previous Message | Josh Kupershmidt | 2011-11-17 22:39:40 | Re: psql + libedit command history truncation (was: psql history vs. dearmor (pgcrypto)) |