Re: Separate GUC for replication origins - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: Separate GUC for replication origins
Date
Msg-id 0c3ae387-e9f2-4bde-b031-a78ce5ce3431@app.fastmail.com
Whole thread Raw
In response to Re: Separate GUC for replication origins  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Fri, Mar 7, 2025, at 11:47 AM, Peter Eisentraut wrote:
Is that maximum active for the whole system, or maximum active per 
session, or maximum active per created origin, or some combination of these?


It is a cluster-wide setting. Similar to max_replication_slots. I will make
sure the GUC description is clear about it. It seems the Replication Progress
Tracking chapter needs an update to specify this information too.


--
Euler Taveira

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Refactoring postmaster's code to cleanup after child exit
Next
From: Andrei Lepikhov
Date:
Subject: Re: Add Postgres module info