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

From Tom Lane
Subject Re: Data corruption/loss when altering tables (fwd)
Date
Msg-id 18183.1101156265@sss.pgh.pa.us
Whole thread Raw
In response to Re: Data corruption/loss when altering tables (fwd)  (Michael Fuhr <mike@fuhr.org>)
Responses Re: Data corruption/loss when altering tables (fwd)
List pgsql-bugs
Michael Fuhr <mike@fuhr.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

pgsql-bugs by date:

Previous
From: Nicola Pero
Date:
Subject: Re: Data corruption/loss when altering tables (fwd)
Next
From: Tom Lane
Date:
Subject: Re: pg_ctl -w start does not know that it has started postmaster