Re: Commitfest 2023-03 starting tomorrow! - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Commitfest 2023-03 starting tomorrow!
Date
Msg-id ZBz721oMVHRQiZw+@paquier.xyz
Whole thread Raw
In response to Re: Commitfest 2023-03 starting tomorrow!  (Greg Stark <stark@mit.edu>)
Responses Re: Commitfest 2023-03 starting tomorrow!  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Thu, Mar 23, 2023 at 04:41:39PM -0400, Greg Stark wrote:
> * Move backup-related code to xlogbackup.c/.h
>   - It looks like neither Alvaro Herrera nor Michael Paquier are
> particularly convinced this is an improvement and nobody has put more
> time in this since last October. I'm inclined to mark this Rejected?

Agreed.

>> * Check consistency of GUC defaults between .sample.conf and pg_settings.boot_val
>   - It looks like this was pretty active until last October and might
> have been ready to apply at least partially? But no further work or
> review has happened since.

FWIW, I don't find much appealing the addition of two GUC flags for
only the sole purpose of that, particularly as we get a stronger
dependency between GUCs that can be switched dynamically at
initialization and at compile-time.

>> * Non-replayable WAL records through overflows and >MaxAllocSize lengths
>
>   - Andres says it's a bug fix

It is a bug fix.  Something I would dare backpatch?  Perhaps not.  The
hardcoded limit of MaxXLogRecordSize makes me feel a bit
uncomfortable, though perhaps we could live with that.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Commitfest 2023-03 starting tomorrow!
Next
From: Peter Smith
Date:
Subject: Re: Data is copied twice when specifying both child and parent table in publication