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

From Euler Taveira
Subject Re: Separate GUC for replication origins
Date
Msg-id 8cac3b29-e676-4fc0-a386-6e9b6fc484ed@app.fastmail.com
Whole thread Raw
In response to Re: Separate GUC for replication origins  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Separate GUC for replication origins
List pgsql-hackers
On Wed, Feb 5, 2025, at 1:56 AM, Amit Kapila wrote:
On Wed, Feb 5, 2025 at 8:17 AM Euler Taveira <euler@eulerto.com> wrote:
>
> Under reflection, an accurate name is max_replication_origin_session_setup. A
> counter argument is that it is a long name (top-5 length).
>
> postgres=# select n, length(n) from (values('max_replication_origins'),
> ('max_tracked_replication_origins'),('max_replication_origin_states'),
> ('max_replication_origin_session_setup')) as gucs(n);
>                   n                   | length
> --------------------------------------+--------
> max_replication_origins              |     23
> max_tracked_replication_origins      |     31
> max_replication_origin_states        |     29
> max_replication_origin_session_setup |     36
> (4 rows)
>

The other possibility is max_replication_origin_sessions.

Looks reasonable to me.

Opinions?


--
Euler Taveira

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: new commitfest transition guidance
Next
From: Masahiko Sawada
Date:
Subject: Re: Separate GUC for replication origins