On Wed, Jul 10, 2024 at 11:52:33PM -0300, Euler Taveira wrote: > On Wed, Jul 10, 2024, at 7:05 PM, Nathan Bossart wrote: >> Unfortunately, I think we have to keep this workaround since older minor >> releases of PostgreSQL don't have the fix. > > Hmm. Right.
On second thought, maybe we should just limit this improvement to the minor releases with the fix so that we _can_ get rid of the workaround. Or we could use the hacky workaround only for versions with the bug. -- nathan
