Re: - Proposal for repreparing prepared statements

From: "Marshall, Steve" <smarshall(at)wsi(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: - Proposal for repreparing prepared statements
Date: 2006-09-13 21:40:51
Message-ID: 8536F69C1FCC294B859D07B179F0694405D10492@EXCHANGE.ad.wsicorp.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

But forcing a reload of pltcl.so is nothing but a kluge --- it leaks
memory like there's no tomorrow, and it's only an accident that it fails
to crash. I don't want to design a further kluge on top of it.

Are you saying that pltcl.so leaks memory in general, or that forcing a
reload of the pltcl.so library leaks memory? If the former, I haven't
seen evidence of it in my use of pltcl, but I'd be interested to know
ofo problems other have had with it.

Yours,
Steve Marshall

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-13 22:03:39 Re: Inconsistency in extended-query-protocol logging
Previous Message Tom Lane 2006-09-13 21:38:33 Re: Optimizer improvements: to do or not to do?