pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Ben Cornett <ben@lantern.is>
Cc: pgsql-bugs@lists.postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: BUG #16112: large, unexpected memory consumption
Date: Mon, 20 Apr 2020 11:55:30 -0700
Message-ID: <20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de> (raw)
In-Reply-To: <20200411183552.u64s3w4nzvroiqxj@development>
References: <16112-4448bbf55a404189@postgresql.org>
	<20191113145004.opxx4vuajyoadbcq@development>
	<20191113170528.caywphoaq45ggqbx@alap3.anarazel.de>
	<368.1573665707@sss.pgh.pa.us>
	<20191113174733.zwfukrx7atfh65t3@alap3.anarazel.de>
	<4328.1573668211@sss.pgh.pa.us>
	<20191115024707.y5bcsb4oo4wzovu4@alap3.anarazel.de>
	<20200409122154.GA90424@shadowdale.lore.is>
	<20200411183552.u64s3w4nzvroiqxj@development>

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





view thread (16+ messages)  latest in thread

Message-ID: <20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de>
Permalink:  ../20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: andres@anarazel.de, tomas.vondra@2ndquadrant.com, ben@lantern.is, tgl@sss.pgh.pa.us
  Subject: Re: BUG #16112: large, unexpected memory consumption
  In-Reply-To: <20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de>
  References: <16112-4448bbf55a404189@postgresql.org> <20191113145004.opxx4vuajyoadbcq@development> <20191113170528.caywphoaq45ggqbx@alap3.anarazel.de> <368.1573665707@sss.pgh.pa.us> <20191113174733.zwfukrx7atfh65t3@alap3.anarazel.de> <4328.1573668211@sss.pgh.pa.us> <20191115024707.y5bcsb4oo4wzovu4@alap3.anarazel.de> <20200409122154.GA90424@shadowdale.lore.is> <20200411183552.u64s3w4nzvroiqxj@development> <20200420185530.kcecu5vafc3icnhk@alap3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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