Re: BUG #16112: large, unexpected memory consumption

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

Hi,

On 2020-04-20 15:19:13 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > 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).
>
> > Yea, I think I'll go for my alternative approach from
> > https://postgr.es/m/20191115024707.y5bcsb4oo4wzovu4%40alap3.anarazel.de
>
> I haven't done any testing, but it looks reasonable.

Thanks for looking. Pushed.

Ben, thanks for the report. And sorry that it took so long.

Greetings,

Andres Freund

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2020-04-23 03:39:34 Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
Previous Message Michael Paquier 2020-04-22 23:46:18 Re: [BUG] non archived WAL removed during production crash recovery