Re: BUG #16112: large, unexpected memory consumption

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Ben Cornett <ben(at)lantern(dot)is>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #16112: large, unexpected memory consumption
Date: 2020-04-20 18:55:30
Message-ID: 20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2020-04-11 20:35:52 +0200, Tomas Vondra wrote:
> On Thu, Apr 09, 2020 at 08:21:54AM -0400, Ben Cornett wrote:

Ben, for the future, it's better to not drop CC addresses etc. I didn't
see this reply at the time you sent it, just when I was catching up on
my backlog of unread postgres email.

> > Did this patch ever get applied? It is not clear to me that it did.

No :(. I lost track of it. I did recall that there was some patch I was
supposed to get back to, but couldn't remember what exactly :(.

It's really too bad that we don't have a bugtracker. I just can't keep
track of all bugs / patches where I e.g. want to wait a few days for a
reply (here to see whether Tom likes my alternative context based
approach).

> Hmmm, I don't think it got applied, which means we've missed yet another
> minor release :-(
>
> Andres, any plans to push this?

Yea, I think I'll go for my alternative approach from
https://postgr.es/m/20191115024707.y5bcsb4oo4wzovu4%40alap3.anarazel.de

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2020-04-20 19:19:13 Re: BUG #16112: large, unexpected memory consumption
Previous Message Tom Lane 2020-04-20 18:48:00 Re: BUG #16378: Invalid memory access on interrupting CLUSTER after CREATE TEMP TABLE