|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Justin Pryzby <pryzby(at)telsasoft(dot)com>|
|Cc:||Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, bruce(at)momjian(dot)us, tgl(at)sss(dot)pgh(dot)pa(dot)us|
|Subject:||Re: GUC flags|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, Feb 07, 2022 at 09:07:28PM -0600, Justin Pryzby wrote:
> I think this is the regex I wrote to handle either "name = value" or "name
> value", which was needed between f47ed79cc..4d7c3e344. See skip_equals.
Yes, I took it from there, noticing that it was working just fine for
> It's fine the way it is, but could also remove the 2nd half of the alternation
> (|), since GUCs shouldn't be added to sample.conf without '='.
Makes sense. check_guc also checks after this pattern.
|Next Message||Julien Rouhaud||2022-02-08 04:22:10||Re: shared_preload_libraries = 'pg_stat_statements' failing with installcheck (compute_query_id = auto)|
|Previous Message||Fujii Masao||2022-02-08 04:00:06||Re: WaitLatchOrSocket seems to not count to 4 right...|