Re: Handle PGRES_COPY_BOTH in psql for logical replication?
От | Andres Freund |
---|---|
Тема | Re: Handle PGRES_COPY_BOTH in psql for logical replication? |
Дата | |
Msg-id | 20150605082242.GO18006@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Handle PGRES_COPY_BOTH in psql for logical replication? ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>) |
Ответы |
Re: Handle PGRES_COPY_BOTH in psql for logical replication?
|
Список | 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?
В списке pgsql-hackers по дате отправления: