| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | update portal-related memory context names and API |
| Date: | 2017-12-19 17:31:44 |
| Message-ID: | 53d4ded9-a1bd-98dc-4475-3763c789cdd4@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
ISTM that some of the portal-related memory context naming is a bit
antiquated and at odds with current terminology. In this patch, I
propose to rename PortalMemory to TopPortalContext and rename
Portal->heap to Portal->portalContext, and then clean up some
surrounding APIs.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Update-portal-related-memory-context-names-and-API.patch | text/plain | 11.4 KB |
| 0002-Remove-PortalGetQueryDesc.patch | text/plain | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-19 18:00:41 | Letting plpgsql in on the fun with the new expression eval stuff |
| Previous Message | Robert Haas | 2017-12-19 16:24:21 | Re: Using ProcSignal to get memory context stats from a running backend |