Robert Haas wrote:
> On Mon, Jun 8, 2009 at 1:06 PM, Bruce Momjian<bruce@momjian.us> wrote:
> > Tom Lane wrote:
> >> Bruce Momjian <bruce@momjian.us> writes:
> >> > At a minimum it would be great if items could mark themselves as
> >> > non-binary-upgradable.
> >>
> >> It's hardly difficult to make that happen --- just change the C name of
> >> some function, or the name of the whole .so file.
> >
> > Yes, but it needs to happen. ?;-) ?PostGIS has done this, which is good.
> > The problem is that if they don't do it it is out of the control of
> > pg_migrator.
>
> I think it might be possible to implement a system that can't be
> broken by accident. Firefox (at least AIUI) requires plugin authors
> to explicitly flag their modules as compatible with new versions of
> Firefox. When you upgrade your firefox installation in place (heh,
> heh) it goes off to the web site and checks whether all of your
> extensions have been so flagged. Any that have not been get disabled
> automatically.
Interesting it allows the flagging to happen in real-time, rather than
requiring the system to know at install time whether it is compatible
with future verions (almost an impossibility). I am afraid we would
need some kind of real-time check, or at least have major versions flag
which external stuff cannot be upgraded, which we have discussed here
already.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +