[Pkg-postgresql-public] Bug#714725: Bug#714725: Consider setting APT::NeverAutoRemove::"postgresql-*" in apt.conf
petere at debian.org
Tue Jul 2 11:44:22 UTC 2013
On 7/2/13 4:26 AM, Christoph Berg wrote:
> The question now is which package(s) should be marked as
> 1) The postgresql-x.y package of the (old)stable release 2)
> ^postgresql-[0-9]+-[0-9]$ 3) ^postgresql-.*
> 2) is probably equivalent to 1), as there's only one version in
> stable, and also easier to maintain, because we don't need to deal
> with changing the file, and partial upgrades.
> 3) would be needed if we decide that we also need to care about
> extension modules that should not be removed on dist-upgrade.
> (Though I tend to think these would usually be manually installed.
> But we might have the same metapackage-with-changing-dependency
> problem there as well.)
It should be 3), because otherwise the postgresql-contrib-x.y package
will be removed and you won't be able to dump your database if it uses
any data type provided in a contrib module. The same goes for things
More information about the Pkg-postgresql-public