Message-ID: <e0df5d73-eac8-836e-d40f-0f2688c13e16@dunslane.net>
Date: Fri, 18 Mar 2022 18:34:25 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: speed up a logical replica setup
Content-Language: en-US
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
 Euler Taveira <euler@eulerto.com>, pgsql-hackers@lists.postgresql.org
References: <5ac50071-f2ed-4ace-a8fd-b892cffd33eb@www.fastmail.com>
 <b9aa614c-84ba-a869-582f-8d5e3ab57424@enterprisedb.com>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <b9aa614c-84ba-a869-582f-8d5e3ab57424@enterprisedb.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/e0df5d73-eac8-836e-d40f-0f2688c13e16%40dunslane.net>
Precedence: bulk


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.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com