| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Brent Tubbs <brent(dot)tubbs(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>, Geoff Tolley <geoff(dot)tolley(at)yougov(dot)com> |
| Subject: | Re: unexpected PQresultStatus: 8 with simple logical replication |
| Date: | 2015-01-10 12:48:36 |
| Message-ID: | CAB7nPqT_MEzATE-i4U12Hw8-WHf=8fEcearNvWhnVAJVYYiCOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jan 10, 2015 at 9:22 AM, Brent Tubbs <brent(dot)tubbs(at)gmail(dot)com> wrote:
> psql "dbname=postgres replication=database user=postgres" -c
> "START_REPLICATION SLOT foobar LOGICAL 0/D9C59A28"
> unexpected PQresultStatus: 8
psql is not smart enough to understand that with a replication connection..
> Advice?
You should use pg_logical_slot_peek_changes or
pg_logical_slot_get_changes to grab changes from a replication slot
using psql. If you are looking at something at a lower level, have a
look at pg_recvlogical as an example of logical change receiver. It is
a good start point as well if your goal is to implement your own
receiver.
In any case, the documentation provides some examples:
http://www.postgresql.org/docs/current/static/logicaldecoding-example.html
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brent Tubbs | 2015-01-10 18:24:56 | Re: unexpected PQresultStatus: 8 with simple logical replication |
| Previous Message | Tomas Vondra | 2015-01-10 01:52:45 | Re: How to analyze a slowdown in 9.3.5? |