Re: update portal-related memory context names and API

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: update portal-related memory context names and API
Date: 2018-01-08 20:30:33
Message-ID: 055481cd-4eb0-1242-ad8b-361f3ae30e83@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/19/2017 12:31 PM, Peter Eisentraut wrote:
> 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.
>

Seems reasonable - 100% cosmetic AFAICT. Marking ready for committer.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-01-08 20:36:38 Re: [HACKERS] Proposal: Local indexes for partitioned table
Previous Message Tomas Vondra 2018-01-08 20:28:55 Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means