Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Given that this problem exists in PG 17, I assume this will not affect
> the PG 18 release this week.
Yeah, if it were 18-only we'd need a powwow about whether to break
release freeze. But since it's been there since 17 and nobody
noticed, I'm content to wait till after 18.0 to fix it.
I believe you need to be superuser to reach the bug at all, otherwise
permissions checks should stop you earlier. This makes it less urgent
than it would otherwise be.
regards, tom lane