Re: pglogical_output - a general purpose logical decoding output plugin
| От | Jarred Ward |
|---|---|
| Тема | Re: pglogical_output - a general purpose logical decoding output plugin |
| Дата | |
| Msg-id | CAMLLTyYFU9_xX6Crz7qDtunvVUTLKAoSHuZyy3dbr83TN4y1-A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: pglogical_output - a general purpose logical decoding output plugin (Craig Ringer <craig@2ndquadrant.com>) |
| Ответы |
Re: pglogical_output - a general purpose logical decoding
output plugin
|
| Список | pgsql-hackers |
I didn't receive a response on the bugs mailing list for the following bug, so I was hoping we could triage to someone with more familiarity with Postgres internals than I to fix.
This ticket seems like folks who are invested in logical decoding.
The attached script is a simple workload that logical decoding is unable to decode. It causes an unrecoverable crash in the logical decoder with 'ERROR: subxact logged without previous toplevel record'.
On Thu, Jan 7, 2016 at 12:44 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
Here's v5 of the pglogical patch.Changes:* Implement relation metadata caching* Add the relmeta_cache_size parameter for cache control* Add an extension to get version information* Create the pglogical_output header directory on install* Restore 9.4 compatibility (it's small)* Allow row filter hooks to see details of the changed tuple* Remove forward_changesets from pglogical_output (use a hook if you want this functionality)I'm not sure if 9.4 compat will be desirable or not. It's handy to avoid needing a separate backported version, but also confusing to do a PGXS build within a 9.6 tree against 9.4...
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: