Re: Added missing invalidations for all tables publication
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
vignesh C <vignesh21@gmail.com>
Date: 2021-09-08T08:27:06Z
Lists: pgsql-hackers
On Wed, Sep 8, 2021 at 7:57 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > > From Mon, Sep 6, 2021 1:56 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > On Tue, Aug 31, 2021 at 8:54 PM vignesh C <vignesh21@gmail.com> wrote: > > > > Thanks for the comments, the attached v3 patch has the changes for > > > > the same. > > > > > > > > > > I think this bug should be fixed in back branches (till v10). OTOH, as > > > this is not reported by any user and we have found it during code > > > review so it seems either users don't have an exact use case or they > > > haven't noticed this yet. What do you people think about back-patching? > > > > Personally, I think it's ok to back-patch. > > I found that the patch cannot be applied to back-branches(v10-v14) cleanly, > so, I generate the patches for back-branches. Attached, all the patches have > passed regression test. > Pushed! -- With Regards, Amit Kapila.
Commits
-
Invalidate relcache for publications defined for all tables.
- 2eb09f27db6c 12.9 landed
- ddfc7299d0a3 13.5 landed
- 8db27fbc1197 14.0 landed
- 8bd534274099 15.0 landed
- 28cde380c1c0 10.19 landed
- 96e38fa5e549 11.14 landed