Re: Data corruption/loss when altering tables (fwd)

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Nicola Pero <n(dot)pero(at)mi(dot)flashnet(dot)it>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Data corruption/loss when altering tables (fwd)
Date: 2004-11-22 17:54:44
Message-ID: 20041122175443.GA81377@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nicola Pero 2004-11-22 18:00:30 Data corruption/loss when altering tables (fwd)
Previous Message Tom Lane 2004-11-22 17:14:30 Re: Data corruption/loss when altering tables (fwd)