RE: long-standing data loss bug in initial sync of logical replication - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: long-standing data loss bug in initial sync of logical replication
Date
Msg-id TYAPR01MB5692ABCD2F1071DA7F84E661F5762@TYAPR01MB5692.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: long-standing data loss bug in initial sync of logical replication  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses Re: long-standing data loss bug in initial sync of logical replication
List pgsql-hackers
> 2.
> Similarly with above, the relcache won't be invalidated when ALTER
> PUBLICATION
> OWNER TO is executed. This means that privilage checks may be ignored if the
> entry
> is still valid. Not sure, but is there a possibility this causes an inconsistency?

Hmm, IIUC, the attribute pubowner is not used for now. The paragpargh
"There are currently no privileges on publications...." [1] may show the current
status. However, to keep the current behavior, I suggest to invalidate the relcache
of pubrelations when the owner is altered.

[1]: https://www.postgresql.org/docs/devel/logical-replication-security.html

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: msys inet_pton strangeness
Next
From: Ashutosh Bapat
Date:
Subject: Re: SET or STRICT modifiers on function affect planner row estimates