Postgresql Email Notice after upgrade to 4.3-0 errata3


We are getting this email alert from our UCS Master Domain Controller and Backup Domain Controller, just wondering what the corrective action should be if any? So far this is only being seen coming from our Master/Backup Domain Controller in UCS, and we are not seeing any adverse impacts. Just wondering if this should be a concern or will be resolved in future UCS updates or if there is action we need to take on our part.

Subject: Debconf: Configuring postgresql-common -- Obsolete major version 9.4

The PostgreSQL version 9.4 is obsolete, but the server or client packages
are still installed. Please install the latest packages (postgresql-9.6
and postgresql-client-9.6) and upgrade the existing  clusters with
pg_upgradecluster (see manpage).

Please be aware that the installation of postgresql-9.6 will automatically
create a default cluster 9.6/main. If you want to upgrade the 9.4/main
cluster, you need to remove the already existing 9.6 cluster
(pg_dropcluster --stop 9.6 main, see manpage for details).

The old server and client packages are no longer supported. After the
existing clusters are upgraded, the postgresql-9.4 and
postgresql-client-9.4 packages should be removed.

Please see /usr/share/doc/postgresql-common/README.Debian.gz for details.



the best course of action is to upgrade to 9.6 following the UCS-specific instructions from the following knowledge base article:

Kind regards,



For the purpose of user impact notifications, what are the potential impacts of this upgrade? I need to put out a change control and am wondering what the end user impact could be.




in my experience for users (as in: applications that use PostgreSQL) there’s no impact at all apart from the downtime during the migration. If the migration works (as in: if the new database clusters exist, contain the databases, the tables, the data), then that’s that. Neither applications nor human beings will notice such a change. Application developers might be happy as they can now use features introduced with newer PostgreSQL versions, but that’s all.

You will have to look out for manual changes you might have applied to the configuration files (postgresql.conf, pg_hba.conf); they’ll have to be migrated manually.

Kind regards,