Re: Separate GUC for replication origins

On Wed, Feb 5, 2025 at 4:39 PM Euler Taveira <euler(at)eulerto(dot)com> wrote:
>
> On Wed, Feb 5, 2025, at 1:56 AM, Amit Kapila wrote:
>
> On Wed, Feb 5, 2025 at 8:17 AM Euler Taveira <euler(at)eulerto(dot)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?

+1

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com