From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Backend memory dump analysis |
Date: | 2018-03-27 17:07:47 |
Message-ID: | 20180327170747.khp4bshsndpyketk@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Great stuff.
My only gripe is the pattern where the identifier needs to be
re-installed when resetting the context. I don't think we need to hold
push for that reason alone, but I bet we'll be revisiting that.
I suppose this infrastructure can be used to implement the idea in
https://www.postgresql.org/message-id/CAMsr+YHii-BCC7ddpbb8fpCgzt0wMRt5GYZ0W_kD_Ft8rwWPiQ@mail.gmail.com
in some more acceptable manner. I'm not proposing it for now, just
parking the idea for a future patch.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-03-27 17:14:49 | Re: WIP: Covering + unique indexes. |
Previous Message | Teodor Sigaev | 2018-03-27 17:07:34 | Re: WIP: Covering + unique indexes. |