Re: Adding column "mem_usage" to view pg_prepared_statements

From: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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: Adding column "mem_usage" to view pg_prepared_statements
Date: 2019-07-30 22:38:50
Message-ID: dd1f09ed-66e5-ae13-6816-69abd225a1b3@ikoffice.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Am 31.07.2019 um 00:29 schrieb Tom Lane:
> 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 ...)

OK, added it there. Thanks for your patience :).

Regards,
Daniel Migowski

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-07-30 22:50:32 Re: Runtime pruning problem
Previous Message Daniel Migowski 2019-07-30 22:32:46 Re: Adding column "mem_usage" to view pg_prepared_statements