| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(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:25:22 |
| Message-ID: | 20150729132522.GC26516@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-07-29 22:21:04 +0900, Michael Paquier wrote:
> On Wed, Jul 29, 2015 at 10:15 PM, Andres Freund wrote:
> > 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.
>
> Actually, you can. CREATE_REPLICATION_SLOT is one of the commands that
> work with psql
I do know that, I wrote the bit in the docs explaining that that's
possible...
But using replication connections that way in psql makes requires it to
be invoked in a different way and makes it it impossible to specify the
database name in a normal way etc. You can also run into commands that
give you 'unexpected result status' errors and such. I don't think
that's a good default interface.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-07-29 14:02:50 | Re: Parallel Seq Scan |
| Previous Message | Michael Paquier | 2015-07-29 13:21:04 | Re: Don'st start streaming after creating a slot in pg_receivexlog |