Re: Separate GUC for replication origins

Euler Taveira <euler@eulerto.com>

From: "Euler Taveira" <euler@eulerto.com>

To: "vignesh C" <vignesh21@gmail.com>

Cc: "Peter Eisentraut" <peter@eisentraut.org>, "Amit Kapila" <amit.kapila16@gmail.com>, "Masahiko Sawada" <sawada.mshk@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2025-03-14T00:54:40Z

Lists: pgsql-hackers

Attachments

v6-0001-Separate-GUC-for-replication-origins.patch (text/x-patch) patch v6-0001
v6-0002-max_active_replication_origins-defaults-to-10.patch.nocfbot (application/octet-stream)

On Thu, Mar 13, 2025, at 11:10 AM, vignesh C wrote:
> Few comments:

Thanks for taking a look.

> 1) After selecting max_active_replication_origins setting in the
> SELECT query having order by, the first record returned will be the
> one with max_active_replication_origins, rather than the second
> record, because max_active_replication_origins appears before
> max_logical_replication_workers in the order.

Fixed.

> 2) I felt max_replication_slots must be max_active_replication_origins
> here in logical-replication.sgml:

Fixed.


--
Euler Taveira
EDB   https://www.enterprisedb.com/

Commits

Add GUC option to control maximum active replication origins.
- 04ff636cbce4 18.0 landed
Better document logical replication parameters
- a8500750ca0a 16.0 cited
Introduce replication progress tracking infrastructure.
- 5aa2350426c4 9.5.0 cited