Re: pgsql: Test replay of regression tests, attempt II.

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Test replay of regression tests, attempt II.
Date: 2022-01-18 22:29:04
Message-ID: CA+hUKGJW8WC=LCJqc=Uyj8A3_oFbbFGXidg6_jP4GSdLTh9T9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Jan 19, 2022 at 11:19 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > Also, it's odd that there's "max_connections 25" without an equal sign. I'd
> > kind of expected that to cause an error....
>
> I see that guc.c intentionally allows the equal sign to be optional.
> Too lazy to check if that's documented. It is weird that this one
> test appears to be intentionally testing that, though, because it's
> sure got nada to do with the expressed purpose of the test.

That's coming from here:

$node_primary->adjust_conf('postgresql.conf', 'max_connections', '25', 1);

That's passed to:

=item $node->adjust_conf(filename, setting, value, skip_equals)

That 1 was unintentional (and I don't see anything else using this
facility), but it doesn't seem to hurt anything since it's parsed just
fine. I'll take it out in passing in a future commit once we figure
out what's up with reloptions...

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2022-01-18 23:08:38 Re: pgsql: Test replay of regression tests, attempt II.
Previous Message Tom Lane 2022-01-18 22:19:06 Re: pgsql: Test replay of regression tests, attempt II.