| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Ashwin Agrawal <ashwinstar(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup --create-slot-if-not-exists? |
| Date: | 2022-09-22 00:46:26 |
| Message-ID: | YyuwYkdSGVVkf90R@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 21, 2022 at 05:34:20PM -0700, David G. Johnston wrote:
> What’s the use case for automating pg_basebackup with a named replication
> slot created by the pg_basebackup command? Why can you not leverage a
> temporary replication slot (i.e., omit —slot). ISTM the create option is
> basically obsolete now.
+1.
Perhaps the ask would ease some monitoring around pg_replication_slots
with a fixed slot name? One thing that could come into play is the
possibility to enforce the use of a temporary slot with a name given
by -S as pg_basebackup makes it permanent in this case, still the
temporary slot name being pg_basebackup_${PID} makes the slot
searchable with a pattern.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-09-22 00:52:57 | Re: make additional use of optimized linear search routines |
| Previous Message | David G. Johnston | 2022-09-22 00:34:20 | Re: pg_basebackup --create-slot-if-not-exists? |