Re: pglogical_output - a general purpose logical decoding output plugin - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: pglogical_output - a general purpose logical decoding output plugin
Date
Msg-id CAMsr+YEGtE8gYnpAo7=n=iMS9OLcc8oeMvMrh+9ki9WB5CykGA@mail.gmail.com
Whole thread Raw
In response to Re: pglogical_output - a general purpose logical decoding output plugin  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: pglogical_output - a general purpose logical decoding output plugin  (Jarred Ward <jarred@webriots.com>)
Re: pglogical_output - a general purpose logical decoding output plugin  (Tomasz Rybak <tomasz.rybak@post.pl>)
Re: pglogical_output - a general purpose logical decoding output plugin  (Tomasz Rybak <tomasz.rybak@post.pl>)
Re: pglogical_output - a general purpose logical decoding output plugin  (Tomasz Rybak <tomasz.rybak@post.pl>)
Re: pglogical_output - a general purpose logical decoding output plugin  (Tomasz Rybak <tomasz.rybak@post.pl>)
List pgsql-hackers

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...

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: pgbench - allow backslash-continuations in custom scripts
Next
From: Craig Ringer
Date:
Subject: Re: pglogical - logical replication contrib module