Hi Ludvig,
Ludvig Janiuk <ludvig.janiuk@proton.me> wrote:
> I'm not familiar with the Postgres bug lifecycle - is there anything
> else I need to do? File a formal bug in some tracker? Or has that
> already happened?
Nothing else is needed from you. PostgreSQL has no separate bug
tracker: this thread on pgsql-bugs is the bug report, and it is already
archived where the committers look.
Fujii posted a patch (v1) in this thread, and it was tested against
master and REL_18_STABLE. As of today it is not committed yet. Once a
committer pushes it, the commit message usually links back to this
thread, and a fix for an 18 regression like this one normally goes into
the next 18.x minor release, where it shows up in the release notes.
If you want to follow it, watching this thread is enough. Thanks for
the clear report with a reproducer, it made the bisect straightforward.
Regards,
Manu
