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

From Andres Freund
Subject Re: Inaccuracy in VACUUM's tuple count estimates
Date
Msg-id 20140609141934.GD3149@alap3.anarazel.de
Whole thread Raw
In response to Re: Inaccuracy in VACUUM's tuple count estimates  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Inaccuracy in VACUUM's tuple count estimates  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2014-06-09 10:14:32 -0400, Robert Haas wrote:
> On Fri, Jun 6, 2014 at 3:44 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > It did not use to blow this question off: back around 8.3 you got
> > DELETE_IN_PROGRESS if the tuple had a delete pending.  I think we need
> > less laziness + fuzzy thinking here.  Maybe we should have a separate
> > HEAPTUPLE_INSERT_AND_DELETE_IN_PROGRESS result code?  Is it *really*
> > the case that callers other than VACUUM itself are okay with failing
> > to make this distinction?
> 
> 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?

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Supporting Windows SChannel as OpenSSL replacement
Next
From: Andres Freund
Date:
Subject: Re: Supporting Windows SChannel as OpenSSL replacement