Re: fedora & postgresql have bad behavior

On Tue, 2008-05-06 at 06:14 -0700, earonesty wrote:
> is there any way to create a repository so that yum does the "correct thing"
> with postgresql & fedora?
> 
> with postgresql, every time the "data format" changes, i'd want yum to
> update *within* the minor version numbers currently installed (8.2.X,
> patches, etc) but not to switch to the highest version for my platform
> (8.3.X) in the repository.
> 
> the reason is that i'd like yum to update security patched every night,
> unattended, but, with postgres, this would have the undesireable effect of
> shutting my database server down every time the minor version changes
> 
> currently my solution is to exclude=postgresql and then look at it every
> once in a while.  but that's a pretty big security risk, since my attendance
> varies.
> 
> (postgresql minor versions are supported and patched in separate forks (much
> like operating systems), so that operators don't have to upgrade until their
> "ready" to dump the database, upgrade, and rebuild.)

You can certainly exclude postgresql from your fedora and updates repos
and then make your own repo for the updates you want to apply. But if
you want more api/abi interface control you might consider using
centos/rhel instead of fedora.

the only other option I can suggest is to make your exclude line more
specific. For example:

exclude=postgresql*-8.3.*

which would allow 8.2.x updates to come in, but not allow 8.3.* changes.

You could also setup a cron job to let you know about postgresql
changes:

yum --disableexcludes=all list available postgresql

maybe these options will help.

-sv