| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Separate GUC for replication origins |
| Date: | 2025-03-07 15:51:16 |
| Message-ID: | 0c3ae387-e9f2-4bde-b031-a78ce5ce3431@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2025-03-07 15:56:41 | Re: Add Postgres module info |
| Previous Message | Andres Freund | 2025-03-07 15:49:44 | Re: Refactoring postmaster's code to cleanup after child exit |