Re: [HACKERS] Logical decoding - filtering tables - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] Logical decoding - filtering tables
Date
Msg-id CAMsr+YGpUQteu2BQZugK5QU8a-tvESOkQ7ZNUi5QMTd-BP7GMw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Logical decoding - filtering tables  (valeriof <valerio_farruggio@hotmail.com>)
List pgsql-hackers
On 3 January 2017 at 21:32, valeriof <valerio_farruggio@hotmail.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



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Shrink volume of default make output
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Odd behavior with PG_TRY