Re: Fix publisher-side sequence permission reporting - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Fix publisher-side sequence permission reporting
Date
Msg-id CAHGQGwE95GLD7RZr2g=zTHKJRafKACmKouhb4TTVH155Hy8zKA@mail.gmail.com
Whole thread
In response to Re: Fix publisher-side sequence permission reporting  ("Tristan Partin" <tristan@partin.io>)
Responses Re: Fix publisher-side sequence permission reporting
List pgsql-hackers
On Fri, Jun 19, 2026 at 8:11 AM Tristan Partin <tristan@partin.io> wrote:
> The patch looks good to me! I had one suggestion:
>
> >  ##########
> >  # Ensure that insufficient privileges on the publisher for a sequence do not
> > -# disrupt the subscriber. The subscriber should log a warning and continue
> > -# retrying.
> > +# get misreported as a missing sequence. The subscriber should log a warning
> > +# and continue retrying.
> >  ##########
>
> I think a better comment might be:
>
>         Ensure that insufficient privileges on the publisher for a sequence
>         are reported correctly...
>
> My reasoning for suggesting that is because your comment would to
> indicate that any warning is accurate as long as it isn't related to
> a missing sequence.

Thanks for the review! I've updated the patch as suggested.

Updated patches attached.

Regards,

--
Fujii Masao

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: use of SPI by postgresImportForeignStatistics
Next
From: Tom Lane
Date:
Subject: Re: fix pg_mkdir_p to tolerate concurrent directory creation