From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Curing plpgsql's memory leaks for statement-lifespan values |
Date: | 2016-07-26 02:54:39 |
Message-ID: | CA+TgmoYdovO69cEtd0UnYs57juSDN4gFX_+fe73P9TihS3gf2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 25, 2016 at 6:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I suppose that a fix based on putting PG_TRY blocks into all the affected
> functions might be simple enough that we'd risk back-patching it, but
> I don't really want to go that way.
try/catch blocks aren't completely free, either, and PL/pgsql is not
suffering from a deplorable excess of execution speed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-07-26 03:12:24 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |
Previous Message | Michael Paquier | 2016-07-26 02:09:58 | Re: AdvanceXLInsertBuffer vs. WAL segment compressibility |