Re: Autovacuum breakage from a734fd5d1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Autovacuum breakage from a734fd5d1
Date: 2016-11-28 03:30:09
Message-ID: 5645.1480303809@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I think you made this considerably more fragile with those changes.

This code will only ever run at all in corner cases --- cases that
almost by definition will go untested in the standard regression tests.
The problems you suggest it has are corner-squared or corner-cubed cases.
We were rather fortunate to find the bugs in the committed version before
it got into the field, and would be even less likely to find bugs in code
that is meant to run in corner-squared cases. So, with all due respect,
I think your priorities here are entirely backwards. I'm much more
worried about whether the code will still work as intended after the next
big backend code refactoring than about whether it's optimal for cases
that will almost never occur in the field.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2016-11-28 03:44:27 Re: UNDO and in-place update
Previous Message Michael Paquier 2016-11-28 03:26:00 Re: Autovacuum breakage from a734fd5d1