From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | valeriof <valerio_farruggio(at)hotmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logical decoding - filtering tables |
Date: | 2017-01-04 03:15:16 |
Message-ID: | CAMsr+YGpUQteu2BQZugK5QU8a-tvESOkQ7ZNUi5QMTd-BP7GMw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3 January 2017 at 21:32, valeriof <valerio_farruggio(at)hotmail(dot)com> wrote:
> Craig Ringer-3 wrote
>> Take a look at how pglogical does it in its replication set handling
>> and relation metadata cache.
>
> I checked it out but for what I understand it uses the inline parameter.
It specifies which replication sets to use with logical decoding parameters.
Those are in turn looked up in user-catalog tables to find mappings of
relations to replication sets.
A cache is used to avoid reading those tables for every tuple.
> Would it be possible to store this info in some config table and then run a
> select from inside the plugin?
Yes, that's what pglogical does.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2017-01-04 03:20:14 | Re: Odd behavior with PG_TRY |
Previous Message | Craig Ringer | 2017-01-04 03:03:37 | Re: Shrink volume of default make output |