Re: Commitfest 2023-03 starting tomorrow!

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Greg Stark <stark(at)mit(dot)edu>, "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Commitfest 2023-03 starting tomorrow!
Date: 2023-03-24 01:59:57
Message-ID: ZB0EHVMRCjCGkVHT@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 24, 2023 at 10:24:43AM +0900, Michael Paquier wrote:
> >> * 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,

The flags seem independently interesting - adding them here follows
a suggestion Andres made in response to your complaint.
20220713234900(dot)z4rniuaerkq34s4v(at)awork3(dot)anarazel(dot)de

> particularly as we get a stronger
> dependency between GUCs that can be switched dynamically at
> initialization and at compile-time.

What do you mean by "stronger dependency between GUCs" ?

--
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2023-03-24 02:13:56 Re: Data is copied twice when specifying both child and parent table in publication
Previous Message Justin Pryzby 2023-03-24 01:50:50 Re: Improve logging when using Huge Pages