| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: portal pinning |
| Date: | 2018-01-09 01:28:57 |
| Message-ID: | 9cee8102-5204-3b2e-d5fe-c87137df244d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/8/18 15:27, Andrew Dunstan wrote:
> This seems like a good idea, and the code change is tiny and clean. I
> don't know of any third party PLs or other libraries might be pinning
> the portals already on their own. How would they be affected if they did?
They would get an error if they tried to pin it a second time. So this
would require a small source-level adjustment. But I doubt this is
actually the case anywhere, seeing that we are not even using this
consistently in core.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-01-09 01:29:52 | Re: proposal: alternative psql commands quit and exit |
| Previous Message | Tom Lane | 2018-01-09 01:20:09 | Re: Unimpressed with pg_attribute_always_inline |