From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Euler Taveira <euler(at)eulerto(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: speed up a logical replica setup |
Date: | 2022-03-22 01:44:33 |
Message-ID: | CAFcNs+qFWFxOh1zP0XUarGsv4eY5jzbbFB5KkXtahBMY0A48FQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 18 Mar 2022 at 19:34 Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 3/15/22 09:51, Peter Eisentraut wrote:
> > On 21.02.22 13:09, Euler Taveira wrote:
> >> A new tool called pg_subscriber does this conversion and is tightly
> >> integrated
> >> with Postgres.
> >
> > Are we comfortable with the name pg_subscriber? It seems too general.
> > Are we planning other subscriber-related operations in the future? If
> > so, we should at least make this one use a --create option or
> > something like that.
>
>
> Not really sold on the name (and I didn't much like the name
> pglogical_create_subscriber either, although it's a cool facility and
> I'm happy to see us adopting something like it).
>
> ISTM we should have a name that conveys that we are *converting* a
> replica or equivalent to a subscriber.
>
>
Some time ago I did a POC on it [1] and I used the name pg_create_subscriber
[1]
https://github.com/fabriziomello/pg_create_subscriber
--
Fabrízio de Royes Mello
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-03-22 01:48:21 | Re: Commitfest manager for 2022-03 |
Previous Message | Andres Freund | 2022-03-22 01:41:33 | Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not? |