| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: speed up a logical replica setup |
| Date: | 2023-11-07 21:00:39 |
| Message-ID: | da078f11-d2de-420e-9611-f3b7d4dadd9a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23.10.23 05:53, Euler Taveira wrote:
> Let's continue with the bike shedding... I agree with Peter E that this name
> does not express what this tool is. At the moment, it only have one action:
> create. If I have to suggest other actions I would say that it could support
> switchover option too (that removes the infrastructure created by this
> tool).
> If we decide to keep this name, it should be a good idea to add an option to
> indicate what action it is executing (similar to pg_recvlogical) as
> suggested
> by Peter.
Speaking of which, would it make sense to put this tool (whatever the
name) into the pg_basebackup directory? It's sort of related, and it
also shares some code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-11-07 21:00:59 | Re: Compiler warning on Debian 12, PostgreSQL 16 Beta3 |
| Previous Message | Stephen Frost | 2023-11-07 20:55:48 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |