On Wed, Jul 14, 2021 at 10:29 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 17104
> Logged by: Ben Sylvain
> Email address: ben1245_111@hotmail.fr
> PostgreSQL version: 11.5
> Operating system: Linux redhat 7
> Description:
>
> hi
>
> please consider bug 15700
> https://granicus.if.org/pgbugs/15700
>
> with high priority.
>
> This bug caused us a big financial and personal trouble.
> we downgraded all environments to v10 cause of that.
Please refer to the actual bug report when referencing existing bugs,
rather than some unaffiliated third party site. Also, please don't
open a new bug just to ask about an old bug. Instead, ask about the
old bug...
And according to the very link that you posted, this bug was fixed
back in 2019. Looks like the fix was in 11.3.
So if you're seeing similar problems on 11.5, you need to file that as
a separate bug and include the steps to reproduce it showing that it's
still there.
And in either case, 11.5 is *way* out of date. On PostgreSQL 11, your
first attempt should be to run it on 11.12 and see if the problem
still exists there.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/