Re: Column Filtering in Logical Replication

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Column Filtering in Logical Replication
Date: 2021-09-16 14:36:32
Message-ID: 202109161436.3z5fhpsalhs3@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021-Sep-16, Alvaro Herrera wrote:

Actually, something like this might be better:

> PublicationObjSpec:

> | TABLE qualified_name
> {
> $$ = makeNode(PublicationObjSpec);
> $$->pubobjtype = PUBLICATIONOBJ_TABLE;
> $$->pubrvobj = $2;
> $$->location = @1;
> }
> | ALL TABLES IN_P SCHEMA name
> {
> $$ = makeNode(PublicationObjSpec);
> $$->pubobjtype = PUBLICATIONOBJ_ALL_TABLES_IN_SCHEMA;
> $$->pubplainobj = $5;
> $$->location = @1;
> }

So you don't have to cram the schema name in a RangeVar, which would
indeed be quite awkward. (I'm sure you can come up with better names
for the struct members there ...)

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Porque francamente, si para saber manejarse a uno mismo hubiera que
rendir examen... ¿Quién es el machito que tendría carnet?" (Mafalda)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2021-09-16 14:38:04 Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead
Previous Message Laurenz Albe 2021-09-16 13:55:07 Re: pgstat_send_connstats() introduces unnecessary timestamp and UDP overhead