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

From Hayato Kuroda (Fujitsu)
Subject RE: Fix publisher-side sequence permission reporting
Date
Msg-id OS9PR01MB12149D8AFCC23CE88858F8D9FF5F82@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread
In response to Re: Fix publisher-side sequence permission reporting  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Dear Vignesh,

> There was an issue reported by Noah at [1], the finding-7 reported
> fails with an assert. The assertion can be triggered if a sequence is
> dropped concurrently while the sequence synchronization worker is
> processing it:

Also, there is a BF failure due to the same reason [1]. At line 269 in the test
we dropped the sequence. If the sequencesync worker has already read the sequence
info at that time, the crash can happen. The point here was that sequencesync
worker could be re-started to try synchronizing sequences which had
insufficient privileges.

BTW, I agree the fix.

[1]: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=culicidae&dt=2026-07-15%2007%3A54%3A30

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Proposal: new file format for hba/ident/hosts configuration?
Next
From: Rafia Sabih
Date:
Subject: Re: Bypassing cursors in postgres_fdw to enable parallel plans