Re: Data is copied twice when specifying both child and parent table in publication

From: vignesh C <vignesh21(at)gmail(dot)com>
To: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>
Subject: Re: Data is copied twice when specifying both child and parent table in publication
Date: 2021-12-07 12:23:00
Message-ID: CALDaNm0=VZSaqFWettOdHja=YCohWVnFhOT2C1RnkG_tyYcphQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 3, 2021 at 11:24 AM houzj(dot)fnst(at)fujitsu(dot)com
<houzj(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Thursday, December 2, 2021 4:54 PM houzj(dot)fnst(at)fujitsu(dot)com <houzj(dot)fnst(at)fujitsu(dot)com> wrote:
> > On Thursday, December 2, 2021 12:50 PM Amit Kapila
> > <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > > On Thu, Dec 2, 2021 at 9:41 AM Greg Nancarrow <gregn4422(at)gmail(dot)com>
> > > wrote:
> > > >
> > > > On Thu, Dec 2, 2021 at 1:48 PM Greg Nancarrow <gregn4422(at)gmail(dot)com>
> > > wrote:
> > > > >
> > > > > If you updated my original description to say "(instead of just
> > > > > the individual partitions)", it would imply the same I think.
> > > > > But I don't mind if you want to explicitly state both cases to make it clear.
> > > > >
> > > >
> > > > For example, something like:
> > > >
> > > > For publications of partitioned tables with
> > > > publish_via_partition_root set to true, only the partitioned table
> > > > (and not its partitions) is included in the view, whereas if
> > > > publish_via_partition_root is set to false, only the individual partitions are
> > included in the view.
> > > >
> > >
> > > Yeah, that sounds good to me.
> >
> > It looks good to me as well.
> > Attach the patches for (HEAD~13) which merge the suggested doc change. I
> > prepared the code patch and test patch separately to make it easier for
> > committer to confirm.
>
> It seems we might not need to backpatch the doc change, so
> attach another version which remove the doc changes from backpatch patches.

Thanks for the patches, the patch applies and the test passes in head
and the back branches. one minor suggestion:
1) Shall we change:
+ <para>
+ For publications of partitioned tables with
+ <literal>publish_via_partition_root</literal> set to
+ <literal>true</literal>, only the partitioned table (and not its partitions)
+ is included in the view, whereas if
+ <literal>publish_via_partition_root</literal> is set to
+ <literal>false</literal>, only the individual partitions are included in the
+ view.
+ </para>
To:
+ <para>
+ For publications of partitioned tables with
+ <literal>publish_via_partition_root</literal> set to
+ <literal>true</literal>, only the partitioned table (and not its partitions)
+ is included in the view, whereas if
+ <literal>publish_via_partition_root</literal> is set to
+ <literal>false</literal>, only the individual partitions (and not the
+ partitioned table) are included in the
+ view.
+ </para>

2) Any particular reason why the code and tests are backbranched but
not the document changes?

Regards,
Vignesh

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2021-12-07 12:56:55 Re: pg_get_publication_tables() output duplicate relid
Previous Message Masahiko Sawada 2021-12-07 11:36:10 Re: Skipping logical replication transactions on subscriber side