Horton

Re: Separate GUC for replication origins

Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>

View thread View on postgr.es
From: Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>
To: Euler Taveira <euler@eulerto.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers@lists.postgresql.org
Date: 2025-01-23T04:19:29Z
Lists: pgsql-hackers 
Hi Euler,

As you may have already read, separating the max_replication_slots parameter
is also discussed in the following thread.

https://www.postgresql.org/message-id/flat/CAA4eK1KF4MbyWmPj9ctNo8Fiei%3DK91RGYtzV5ELeCvR%3D_rqNgg%40mail.gmail.com#3012c5c18e40e
21ac553b42d53249e42

I agree with separating the parameters.
I think we need to discuss the names of the parameter.
Parameter names were also discussed in the above thread.
It was suggested to name them 'max_replication_origin_states' or
'max_tracked_replication_origins'.

Personally, I find 'max_replication_origin_states' easier to understand,
although it is a long name.

Best Regards,
Keisuke Kuroda
NTT Comware

Commits

  1. Add GUC option to control maximum active replication origins.

  2. Better document logical replication parameters

  3. Introduce replication progress tracking infrastructure.