Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database - Mailing list pgsql-bugs

From Dilip Kumar
Subject Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database
Date
Msg-id CAFiTN-uu5htStpMN+2z6Mjb2-3cjcoD0V50GxqoQ7bHa15h-OQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database  (vignesh C <vignesh21@gmail.com>)
List pgsql-bugs
On Sun, Aug 17, 2025 at 7:23 PM vignesh C <vignesh21@gmail.com> wrote:
>
> > PFA, updated patches for v13 to head, make check-world is passing for
> > all the branches for v15+ we had upgrade test which also run
> > regression test so we additionally have to set max_wal_senders=1 for
> > 002_pg_upgrade.pl
>
> Do you feel it will be better to append the configurations using
> single call like below:
> -$oldnode->append_conf('postgresql.conf', 'log_statement = none');
> -$oldnode->append_conf('postgresql.conf', 'wal_level = replica');
> -$oldnode->append_conf('postgresql.conf', 'max_wal_senders = 1');
> +$oldnode->append_conf(
> +       'postgresql.conf',
> +       qq{log_statement = 'none'
> +       wal_level = 'replica'
> +       max_wal_senders = 1});

Not sure if one way is superior over another or preferred.  I see both
sorts of usage patterns throughout our test suit.

--
Regards,
Dilip Kumar
Google



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19022: Trying to set up pem server not accepting any passwords
Next
From: vignesh C
Date:
Subject: Re: BUG #18988: DROP SUBSCRIPTION locks not-yet-accessed database