Re: Data corruption/loss when altering tables (fwd) - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: Data corruption/loss when altering tables (fwd)
Date
Msg-id 20041122175443.GA81377@winnie.fuhr.org
Whole thread Raw
In response to Re: Data corruption/loss when altering tables (fwd)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Data corruption/loss when altering tables (fwd)
List pgsql-bugs
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 to get rid of the obsolete cached plan.

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?
It appears to work that way in simple tests -- are there situations
where that wouldn't work?

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

pgsql-bugs by date:

Previous
From: Nicola Pero
Date:
Subject: Re: Data corruption/loss when altering tables (fwd)
Next
From: Michael Fuhr
Date:
Subject: Re: Data corruption/loss when altering tables (fwd)