Re: Handle PGRES_COPY_BOTH in psql for logical replication?

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Handle PGRES_COPY_BOTH in psql for logical replication?
Date: 2015-06-05 08:22:42
Message-ID: 20150605082242.GO18006@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2015-06-05 09:43:45 +0200, Shulgin, Oleksandr wrote:
> > How would that look like? It's just binary data you'd get back? And what
> > would be the feedback messages and such look like, and what would be the
> > content?

> It would be whatever the logical decoding plugin sends. Makes perfect
> sense for OUTPUT_PLUGIN_TEXTUAL_OUTPUT to see it on the terminal. And you
> could even use binary with psql's \o, if you want (though usefulness is
> less apparent to me in this case).

Hm. I severely doubt that that's a useful thing to do.

> > For example, one could try replication from different wal positions,
> > > different output plugins and/or plugin options, w/o re-establishing the
> > > connection, interactively by editing the command directly in psql prompt,
> > > as opposed to using pg_recvlogical and editing the command line switches.
> >
> > You can mostly use the sql functions for that.
> >
>
> Maybe I'm missing something, which functions do you have in mind exactly?

pg_logical_slot_get_changes() etc?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shulgin, Oleksandr 2015-06-05 08:59:33 Re: Handle PGRES_COPY_BOTH in psql for logical replication?
Previous Message Shulgin, Oleksandr 2015-06-05 07:43:45 Re: Handle PGRES_COPY_BOTH in psql for logical replication?