[HACKERS] Handle PGRES_COPY_BOTH in psql for logical replication?

2015-06-05 Thread Shulgin, Oleksandr
Hello Hackers, At the moment one can open up a replication connection using psql and use all of the commands available on this special type of connection, except for START_REPLICATION: $ psql -d dbname=test replication=database psql (9.4.1) Type help for help. test=# IDENTIFY_SYSTEM;

Re: [HACKERS] Handle PGRES_COPY_BOTH in psql for logical replication?

2015-06-05 Thread Shulgin, Oleksandr
On Fri, Jun 5, 2015 at 10:22 AM, Andres Freund and...@anarazel.de wrote: Maybe I'm missing something, which functions do you have in mind exactly? pg_logical_slot_get_changes() etc? Oh, totally forgot about these. However there are two significant differences between using the functions

Re: [HACKERS] Handle PGRES_COPY_BOTH in psql for logical replication?

2015-06-05 Thread Andres Freund
On 2015-06-05 09:20:41 +0200, Shulgin, Oleksandr wrote: Hello Hackers, At the moment one can open up a replication connection using psql and use all of the commands available on this special type of connection, except for START_REPLICATION: $ psql -d dbname=test replication=database psql

Re: [HACKERS] Handle PGRES_COPY_BOTH in psql for logical replication?

2015-06-05 Thread Shulgin, Oleksandr
On Fri, Jun 5, 2015 at 9:26 AM, Andres Freund and...@anarazel.de wrote: On 2015-06-05 09:20:41 +0200, Shulgin, Oleksandr wrote: Hello Hackers, At the moment one can open up a replication connection using psql and use all of the commands available on this special type of connection,

Re: [HACKERS] Handle PGRES_COPY_BOTH in psql for logical replication?

2015-06-05 Thread Andres Freund
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