On Mon, Apr 12, 2021 at 4:30 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> As far as I can see there's no reasonable way to disable this
> "optimization", which scares me.
I'm fine with adding a simple 'off' switch. What I'd like to avoid
doing is making the behavior tunable, since it's likely to change in
Postgres 15 and Postgres 16 anyway.
--
Peter Geoghegan