On Mon, Jul 13, 2026 at 09:49:09AM +0200, Laurenz Albe wrote:
> I just wasn't sure if the omission was intentional or not;
> your research says it was a mistake.
The CREATE/DROP requirement makes this issue less of a problem as it
means that a relcache invalidation would happen between the two
queries and we lock the objects, still missing the check was feeling
contrary to the API promise, so applied and backpatched down.
--
Michael