RE: BUG #15067: Documentation or behaviour bug with autovacuum thresholds?

From: Greg Clough <greg(dot)clough(at)ipreo(dot)com>
To: Greg Clough <greg(dot)clough(at)ipreo(dot)com>, Jim Nasby <jim(dot)nasby(at)openscg(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #15067: Documentation or behaviour bug with autovacuum thresholds?
Date: 2018-03-20 17:50:30
Message-ID: MWHPR03MB31335FD5FDC1AF6BCB567698F7AB0@MWHPR03MB3133.namprd03.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> > Obviously that doesn't make sense given your example, so I'm wondering if you did a single-row update some time before step 3.
>
> Hi Jim. No, there were no other updates. I'm glad you agree this is strange.

Using my test case in the last email, can anyone explain why this is actually working "as designed"? It's probably not a big issue, but it's a corner case that's still bugging me.

Cheers,
Greg.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Korotkov 2018-03-21 12:25:11 Re: Fwd: [BUGS] pg_trgm word_similarity inconsistencies or bug
Previous Message PG Bug reporting form 2018-03-20 12:45:50 BUG #15123: pgAdmin 4 no error message