| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| 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: Adding column "mem_usage" to view pg_prepared_statements |
| Date: | 2019-07-30 22:17:40 |
| Message-ID: | 20190730221740.vhnirrnxvtrm67ib@development |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 30, 2019 at 10:01:09PM +0000, Daniel Migowski wrote:
>Hello,
>
>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.
>
Nope. Code freeze for PG12 data was April 7, 2019. You're a bit late for
that, unfortunately. We're in PG13 land now.
FWIW not sure what mail client you're using, but it seems to be breaking
the threads for some reason, splitting it into two - see [1].
Also, please stop top-posting. It makes it way harder to follow the
discussion.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-07-30 22:27:19 | Re: Runtime pruning problem |
| Previous Message | Daniel Migowski | 2019-07-30 22:15:09 | AW: AW: Adding column "mem_usage" to view pg_prepared_statements |