Re: Inaccuracy in VACUUM's tuple count estimates - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Inaccuracy in VACUUM's tuple count estimates
Date
Msg-id 28224.1402324243@sss.pgh.pa.us
Whole thread Raw
In response to Re: Inaccuracy in VACUUM's tuple count estimates  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Inaccuracy in VACUUM's tuple count estimates  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-06-09 10:14:32 -0400, Robert Haas wrote:
>> I think that would be a good idea for conceptual clarity if nothing
>> else.  If callers are OK with it, then they can treat both of those
>> codes alike; but then at least there's clear evidence as to the
>> author's intent.

> I am happy to introduce the code for that. But it'd have to be >=9.4 or
> 9.4?

We need a solution that can be back-patched, unless you're prepared to
revert what you already did to HTSV in the back branches.

Having said that, it's not clear to me that we couldn't change HTSV's
API in the back branches.  What third-party code would be likely to
be depending on it?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Allowing join removals for more join types
Next
From: "MauMau"
Date:
Subject: Re: Supporting Windows SChannel as OpenSSL replacement