| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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:21:04 |
| Message-ID: | CAB7nPqQ6e+DuBC8x06VxcxKRhbW7mp79XDAqyjSHScon4NXJ6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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, but that's not really practical compared to what
pg_recvlogical and pg_receivexlog can do.
$ psql -d "replication=1"
=# CREATE_REPLICATION_SLOT hoge PHYSICAL;
slot_name | consistent_point | snapshot_name | output_plugin
-----------+------------------+---------------+---------------
hoge | 0/0 | null | null
(1 row)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-07-29 13:25:22 | Re: Don'st start streaming after creating a slot in pg_receivexlog |
| Previous Message | Andres Freund | 2015-07-29 13:20:36 | Re: Don'st start streaming after creating a slot in pg_receivexlog |