On Wed, Sep 16, 2026 at 1:21 PM Peter Smith <[email protected]> wrote: > > On Wed, Sep 16, 2026 at 5:41 PM Amit Kapila <[email protected]> wrote: > > > > On Wed, Sep 16, 2026 at 12:23 PM Peter Smith <[email protected]> wrote: > > > > Can you share an example of such a case? > > > > My example was using 'publication relation' (not 'publication excluded > relation') and I've already shared it. > > But that bug (?) already exists because this logic appears only aware > of PUBLICATIONRELMAP rels and is not accounting for FOR ALL TABLES > etc, so it reports an error like > ERROR: "t1" is not a published relation of publication "pub" > even though table public.t1 does exist and really is a published > relation of pub. >
Right, but it is a different case as discussed. So, I would still prefer to keep the same message to keep the code simple. Also, I would like to push this patch after changing the Assert location as pointed by Nisha unless you or others have any other comment. -- With Regards, Amit Kapila.
