Re: AW: AW: Adding column "mem_usage" to view pg_prepared_statements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: AW: AW: Adding column "mem_usage" to view pg_prepared_statements
Date: 2019-07-30 22:29:53
Message-ID: 6885.1564525793@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Daniel Migowski <dmigowski(at)ikoffice(dot)de> writes:
> Ok, just have read about the commitfest thing. Is the patch OK for that? Or is there generally no love for a mem_usage column here? If it was, I really would add some memory monitoring in our app regarding this.

You should certainly put it into the next commitfest. We might or
might not accept it, but if it's not listed in the CF we might
not remember to even review it. (The CF app is really a to-do
list for patches ...)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-07-30 22:32:35 Re: Runtime pruning problem
Previous Message Tom Lane 2019-07-30 22:27:19 Re: Runtime pruning problem