Re: Backend memory dump analysis - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Backend memory dump analysis
Date
Msg-id 20180327170747.khp4bshsndpyketk@alvherre.pgsql
Whole thread Raw
In response to Re: Backend memory dump analysis  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Backend memory dump analysis  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: WIP: Covering + unique indexes.
Next
From: Teodor Sigaev
Date:
Subject: Re: WIP: Covering + unique indexes.