Skip site navigation (1) Skip section navigation (2)

Re: symbol mismatches on minor version upgrades

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: symbol mismatches on minor version upgrades
Date: 2011-09-02 18:58:46
Message-ID: 1314989929.11695.8.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On tis, 2011-08-30 at 15:31 -0400, Tom Lane wrote:
> While not wishing to deny that this can be a problem, I think you're
> overstating this aspect:
> 
> > Now if this had been, say, plpython, which is also developed closely
> > together with the backend, but is probably shipped in a separate binary
> > package and has extra dependencies, so it might reasonably not be
> > upgraded at the same time, there would be additional problems.  We
> > should figure out a way to advise packagers about putting in tight
> > enough version dependencies when this happens.
> 
> This is not possible at least in the Red Hat world, because all the
> subpackages have exact-version-and-release dependencies tying them
> together.  That's distro policy not just my whim, and I'd expect other
> server-grade distros to have similar policies. 

Well, the Debian packages don't do this.  Obviously, they could, but no
one has ever clarified this.

Exactly which distribution policy is this?  I would rather think that
this is something that upstream needs to determine.


In response to

Responses

pgsql-hackers by date

Next:From: Tomas VondraDate: 2011-09-02 19:00:55
Subject: Re: PATCH: regular logging of checkpoint progress
Previous:From: Peter EisentrautDate: 2011-09-02 18:54:07
Subject: Re: sha1, sha2 functions into core?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group