pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17104: memory leak
2+ messages / 2 participants
[nested] [flat]
* BUG #17104: memory leak
@ 2021-07-13 19:37 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2021-07-13 19:37 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: ben1245_111@hotmail.fr
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.
Regards
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17104: memory leak
@ 2021-07-14 09:00 Magnus Hagander <magnus@hagander.net>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Magnus Hagander @ 2021-07-14 09:00 UTC (permalink / raw)
To: ben1245_111@hotmail.fr, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
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/
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2021-07-14 09:00 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-07-13 19:37 BUG #17104: memory leak PG Bug reporting form <noreply@postgresql.org>
2021-07-14 09:00 ` Magnus Hagander <magnus@hagander.net>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox