From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, 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> |
Subject: | Re: [PATCH] Unremovable tuple monitoring |
Date: | 2011-11-17 23:44:34 |
Message-ID: | CA+TgmoZoqde3Z3EFuEDpjd3xaWRBdg=gL77yMsQPToB37Kxnwg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 17, 2011 at 5:49 PM, Royce Ausburn <royce(dot)ml(at)inomial(dot)com> wrote:
> 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.
One question to ask yourself at this point in the process is whether
*you* still think the feature is useful. I'm fairly persuaded by
Tom's point that the value monitored by this patch will change so
quickly that it won't be useful to have VACUUM store it; it'll be
obsolete by the time you look at the numbers. If you are also
persuaded by that argument, then clearly it's time to throw in the
towel!
But let's suppose you're NOT persuaded by that argument and you still
want the feature. In that case, don't just wait for someone else to
stick up for the feature; tell us why you still think it's a good
idea. Make a case for what you want. People here are usually
receptive to good ideas, well-presented.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-11-17 23:45:44 | Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement |
Previous Message | Royce Ausburn | 2011-11-17 22:49:45 | Re: [PATCH] Unremovable tuple monitoring |