Re: why can't a table be part of the same publication as its schema - Mailing list pgsql-hackers

From Peter Smith
Subject Re: why can't a table be part of the same publication as its schema
Date
Msg-id CAHut+PsfEi6CExGCJos=sNjCMgKrL3M3UgP+ZSh97Xn4s04_=w@mail.gmail.com
Whole thread Raw
In response to RE: why can't a table be part of the same publication as its schema  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
List pgsql-hackers
On Thu, Sep 15, 2022 at 10:57 PM houzj.fnst@fujitsu.com
<houzj.fnst@fujitsu.com> wrote:
>
...
> Attach the new version patch which added suggested restriction for column list
> and merged Vignesh's patch.
>
> Some other document might need to be updated. I will update them soon.
>
> Best regards,
> Hou zj

Hi Hou-san.

FYI, I found your v3 patch apply was broken due to a very recent changes pushed:

e.g.
error: patch failed: doc/src/sgml/logical-replication.sgml:1142

~~

PSA a rebase of your same patch (I left the version number the same)

------
Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: walmethods.c/h are doing some strange things