From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Don'st start streaming after creating a slot in pg_receivexlog |
Date: | 2015-07-29 13:15:39 |
Message-ID: | 20150729131539.GA26516@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-07-29 13:53:31 +0100, Simon Riggs wrote:
> It makes more sense to create one new utility to issue replication commands
> than to enhance multiple utility commands to have bizarre looking
> additional features and modes.
>
> pg_reputil --create-slot
> pg_reputil --drop-slot
> etc
Logical slots behave differently than physical slots and need different
options. So to me there's a fair point in having support for
manipulating logical slot in a tool around logical slots.
Additionally that support was there in 9.4 and I know at least of three
scripts that call pg_recvlogical to create logical slots. Admittedly one
of them is of my own creation.
> though I prefer the idea of using psql and the already existing slot
> functions than doing all of this extra code that needs maintaining.
It's not that uncommon to have replicas only access the primary for
replication type connections. So it seems completely sensible to use the
replication protocol to manage slots. And that you can't really do with
psql.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-07-29 13:17:27 | Re: Don'st start streaming after creating a slot in pg_receivexlog |
Previous Message | Andres Freund | 2015-07-29 13:10:18 | Re: LWLock deadlock and gdb advice |