On Mon, Nov 22, 2004 at 03:44:25PM -0500, Tom Lane wrote:
> Michael Fuhr <[EMAIL PROTECTED]> writes:
> > Would LOAD 'plpgsql' work? Would that cause a fresh compile of the
> > function the next time it's called, resulting in a new cached plan?
>
> I think that would cause plpgsql to lose track of
Michael Fuhr <[EMAIL PROTECTED]> writes:
> Would LOAD 'plpgsql' work? Would that cause a fresh compile of the
> function the next time it's called, resulting in a new cached plan?
I think that would cause plpgsql to lose track of its entire function
table, which is a brute force way of doing that
Is there a way to explictly flush cached plans ? Is there a way to
prevent the caching of the plan in the stored procedure ?
You can prevent plan caching in PL/pgSQL by using EXECUTE. See the
"Executing Dynamic Commands" section in the PL/pgSQL chapter of the
documentation.
Thanks! I suppose th
I've been experiencing data corruption/loss in Postgresql 7.4.2.
I tracked this down to altering tables. After I alter a table, I get data
loss (fields becoming NULL with no reason!) unless I restart immediately
the database server. After the restart all seems OK (but the data which
was lost,
On Mon, Nov 22, 2004 at 06:26:09PM +, Nicola Pero wrote:
> Is there a way to explictly flush cached plans ? Is there a way to
> prevent the caching of the plan in the stored procedure ?
You can prevent plan caching in PL/pgSQL by using EXECUTE. See the
"Executing Dynamic Commands" section
On Mon, Nov 22, 2004 at 12:14:30PM -0500, Tom Lane wrote:
> The problem shown in your example is simply that the UPDATE in the
> plpgsql function has cached a plan that applies to the original format
> of the table. You don't need to restart the server, but you do need to
> start a fresh session
I've been experiencing data corruption/loss in Postgresql 7.4.2.
I tracked this down to altering tables. After I alter a table, I get data loss
(fields becoming NULL with no reason!) unless I restart immediately the
database server.
The problem shown in your example is simply that the UPDATE in
Nicola Pero <[EMAIL PROTECTED]> writes:
> I've been experiencing data corruption/loss in Postgresql 7.4.2.
> I tracked this down to altering tables. After I alter a table, I get data
> loss
> (fields becoming NULL with no reason!) unless I restart immediately the
> database server.
The proble
Hello Nicola,
Monday, November 22, 2004, 9:00:30 PM, you wrote:
NP> I've been experiencing data corruption/loss in Postgresql 7.4.2.
Try to recompile (create or replace) your stored procedure
after you alter the table
Hope this help...
--
Best regards,
Ivanmai
This is my third attempt at posting to the list ... hopefully it will make
it this time
-- Forwarded message --
Date: Mon, 22 Nov 2004 04:34:22 + (GMT)
From: Nicola Pero <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Data corruption/loss when altering tables
I've been expe
10 matches
Mail list logo
