Postgres Pro
Downloads
Home   >   mailing lists

Re: Curing plpgsql's memory leaks for statement-lifespan values - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Curing plpgsql's memory leaks for statement-lifespan values
Date
Msg-id CA+TgmoYdovO69cEtd0UnYs57juSDN4gFX_+fe73P9TihS3gf2w@mail.gmail.com
Whole thread Raw
In response to Re: Curing plpgsql's memory leaks for statement-lifespan values  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Curing plpgsql's memory leaks for statement-lifespan values  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Jul 25, 2016 at 6:04 PM, Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: AdvanceXLInsertBuffer vs. WAL segment compressibility
Next
From: Robert Haas
Date:
Subject: Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE