Re: Spurious "apparent wraparound" via SimpleLruTruncate() rounding

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Spurious "apparent wraparound" via SimpleLruTruncate() rounding
Date: 2019-02-11 05:13:49
Message-ID: 20190211051349.GA952299@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 02, 2019 at 03:38:22AM -0500, Noah Misch wrote:
> The main consequence is the false alarm. A prudent DBA will want to react to
> true wraparound, but no such wraparound has occurred. Also, we temporarily
> waste disk space in pg_xact. This feels like a recipe for future bugs. The
> fix I have in mind, attached, is to change instances of
> ctl->PagePrecedes(FIRST_PAGE_OF_SEGMENT, ROUNDED_cutoffPage) to
> ctl->PagePrecedes(LAST_PAGE_OF_SEGMENT, cutoffPage). I'm inclined not to
> back-patch this; does anyone favor back-patching?

To avoid wasting more of anyone's time: that patch is bad; I'll update this
thread when I have something better.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-11 06:31:23 subscriptionCheck failures on nightjar
Previous Message David Rowley 2019-02-11 04:31:54 Re: Inadequate executor locking of indexes