Re: BUG #14057: vacuum setting reltuples=0 for tables with >0 tuples

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14057: vacuum setting reltuples=0 for tables with >0 tuples
Date: 2017-03-16 21:35:55
Message-ID: 20170316213555.fwdnjv5tnrc37pek@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2017-03-16 17:28:24 -0400, Tom Lane wrote:
> Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> > "Andres" == Andres Freund <andres(at)anarazel(dot)de> writes:
> > Andres> Seems like a good thing to include in the tree. I'd be ok with
> > Andres> just including the simpler version in the relevant branches.
>
> > Ok.
>
> I dunno ... there doesn't seem to be any meaningful portability risk
> here, and it's not clear to me what class of future bug this test might
> hope to catch. Do we really need to spend test cycles forevermore on
> this?

We had previous bugs around this, so it doesn't seem like a bad idea to
test it. Also it should be so short in comparison to the rest of the
isolationtests that it won't matter wrt total runtime?

- Andres

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message MauMau 2017-03-16 22:21:24 Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled
Previous Message Tom Lane 2017-03-16 21:28:24 Re: BUG #14057: vacuum setting reltuples=0 for tables with >0 tuples