Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication - Mailing list pgsql-hackers

From Ajin Cherian
Subject Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
Date
Msg-id CAFPTHDbrJJtaR4Jf2HNOZQVyBLJF-kq8kk=FvmeZ1rfU+Y3R5g@mail.gmail.com
Whole thread
In response to Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Responses Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
List pgsql-hackers
On Sun, Mar 8, 2026 at 4:16 AM Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
>
> Hi All,
>
> Submitting a new version of the patch based on Satya's earlier work - [1].
>
> Please take a look and let us know your thoughts.
>
> [1] - https://www.postgresql.org/message-id/CAHg%2BQDfU7rOebrLDESPpHSgdiadKbpCOmBokcbmM6Gr%2BA5VobQ%40mail.gmail.com
>

Hi Ashutosh,

I was testing this patch and it seems, if the name of the slots starts
with first, say firstslot or firstsub, then the patch treats it as
FIRST 1 priority mode.

I tested with this:
synchronized_standby_slots = 'firstsub1, firstsub2'

regards,
Ajin Cherian
Fujitsu Australia



pgsql-hackers by date:

Previous
From: Eduard Stepanov
Date:
Subject: Re: BUG: ReadStream look-ahead exhausts local buffers when effective_io_concurrency>=64
Next
From: Yura Sokolov
Date:
Subject: Re: Why clearing the VM doesn't require registering vm buffer in wal record