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: | AW: AW: Adding column "mem_usage" to view pg_prepared_statements |
Date: | 2019-07-30 22:15:09 |
Message-ID: | 41ED3F5450C90F4D8381BC4D8DF6BBDCF02EC959@EXCHANGESERVER.ikoffice.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Gesendet: Mittwoch, 31. Juli 2019 00:09
An: Daniel Migowski <dmigowski(at)ikoffice(dot)de>
Cc: Andres Freund <andres(at)anarazel(dot)de>; pgsql-hackers(at)lists(dot)postgresql(dot)org
Betreff: Re: AW: Adding column "mem_usage" to view pg_prepared_statements
Daniel Migowski <dmigowski(at)ikoffice(dot)de> writes:
> Will my patch be considered for 12.0? The calculation of the mem_usage value might be improved later on but because the system catalog is changed I would love to add it before 12.0 becomes stable.
v12 has been feature-frozen for months, and it's pretty hard to paint this as a bug fix, so I'd say the answer is "no".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-07-30 22:17:40 | Re: Adding column "mem_usage" to view pg_prepared_statements |
Previous Message | Tom Lane | 2019-07-30 22:09:21 | Re: AW: Adding column "mem_usage" to view pg_prepared_statements |