AW: AW: Adding column "mem_usage" to view pg_prepared_statements
От | Daniel Migowski |
---|---|
Тема | AW: AW: Adding column "mem_usage" to view pg_prepared_statements |
Дата | |
Msg-id | 41ED3F5450C90F4D8381BC4D8DF6BBDCF02EC959@EXCHANGESERVER.ikoffice.de обсуждение исходный текст |
Ответ на | Re: AW: Adding column "mem_usage" to view pg_prepared_statements (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: AW: AW: Adding column "mem_usage" to view pg_prepared_statements
|
Список | 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 columnhere? If it was, I really would add some memory monitoring in our app regarding this. -----Ursprüngliche Nachricht----- Von: Tom Lane <tgl@sss.pgh.pa.us> Gesendet: Mittwoch, 31. Juli 2019 00:09 An: Daniel Migowski <dmigowski@ikoffice.de> Cc: Andres Freund <andres@anarazel.de>; pgsql-hackers@lists.postgresql.org Betreff: Re: AW: Adding column "mem_usage" to view pg_prepared_statements Daniel Migowski <dmigowski@ikoffice.de> writes: > Will my patch be considered for 12.0? The calculation of the mem_usage value might be improved later on but because thesystem 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
В списке pgsql-hackers по дате отправления: