The following is a proposal for work I'd like to do to force
long-running backend processes to reprepare their prepared statements.
It would be used in cases where the user knows they have made a database
change that will invalidate an existing prepared statement.
I look forward to comments
Stephen Marshall [EMAIL PROTECTED] writes:
The following is a proposal for work I'd like to do to force
long-running backend processes to reprepare their prepared statements.
It would be used in cases where the user knows they have made a database
change that will invalidate an existing
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 2:08 PM
To: Marshall, Steve
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] - Proposal for repreparing prepared statements
Stephen Marshall [EMAIL PROTECTED] writes:
The following is a proposal for work I'd like to do to force
Marshall, Steve [EMAIL PROTECTED] writes:
1. Is the invalidation of stored plans going to be part of 8.2? If not,
any idea when it would be available? I'd be willing to work on this, if
it would help.
No, it did not get done; feel free to work on it for 8.3.
2. Is there any plan for the
Marshall, Steve [EMAIL PROTECTED] writes:
1. Is the invalidation of stored plans going to be part of 8.2? If
not, any idea when it would be available? I'd be willing to work on
this, if it would help.
No, it did not get done; feel free to work on it for 8.3.
[steve's reply]:
Could you
Marshall, Steve [EMAIL PROTECTED] writes:
I want to be able to tell a backend to reinitialize some of the cached
data it is holding in static variables. Generally I want to do this
when the something cached in memory has gotten out-of-sync with what
is in the database. The two examples that
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
Marshall, Steve [EMAIL PROTECTED] writes:
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
