Re: Adding column "mem_usage" to view pg_prepared_statements - Mailing list pgsql-hackers

From Daniel Migowski
Subject Re: Adding column "mem_usage" to view pg_prepared_statements
Date
Msg-id dd1f09ed-66e5-ae13-6816-69abd225a1b3@ikoffice.de
Whole thread Raw
In response to Re: AW: AW: Adding column "mem_usage" to view pg_prepared_statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Adding column "mem_usage" to view pg_prepared_statements  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
Am 31.07.2019 um 00:29 schrieb Tom Lane:
> Daniel Migowski <dmigowski@ikoffice.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_usagecolumn 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




pgsql-hackers by date:

Previous
From: Daniel Migowski
Date:
Subject: Re: Adding column "mem_usage" to view pg_prepared_statements
Next
From: Tom Lane
Date:
Subject: Re: Runtime pruning problem