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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Fuhr <mike(at)fuhr(dot)org>
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 20:44:25
Message-ID: 18183.1101156265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Fuhr <mike(at)fuhr(dot)org> 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 ... but it doesn't
really solve Nicola's problem, because the nasty part of this is
plans that are already cached by other backends.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-11-22 21:16:15 Re: pg_ctl -w start does not know that it has started postmaster
Previous Message David B 2004-11-22 20:20:39 Getting weird results with unicode table...