Fwd: Need older (9.6~beta1-2.pgdg16.04+1) postgres beta packages - Mailing list pgsql-admin

From Anonymous Anonymous
Subject Fwd: Need older (9.6~beta1-2.pgdg16.04+1) postgres beta packages
Date
Msg-id 155864ab0c6.ce51248b249809.7661358610799377206@hda.me
Whole thread Raw
In response to Need older (9.6~beta1-2.pgdg16.04+1) postgres beta packages  (Anonymous Anonymous <admin@hda.me>)
List pgsql-admin
Problem solved.
I rebuilded packages from postgresql-9.6beta1.tar.gz source. Made pd-dump and migrated to stable postgres version. Still will be running beta on another port, but not for production anymore.
============ Forwarded message ============
From : <admin@hda.me>
To : <pgsql-admin@postgresql.org>
Date : Sat, 25 Jun 2016 06:56:17 +0200
Subject : Need older (9.6~beta1-2.pgdg16.04+1) postgres beta packages
============ Forwarded message ============
I need update cluster to new postgres version. The database cluster was initialized with CATALOG_VERSION_NO 201605051, but the server was compiled with CATALOG_VERSION_NO 201606171.
/var/cache/apt/archives was mounted to tmpfs.
Full list of packages I need:
 postgresql-common:amd64 174.pgdg16.04+1 postgresql-client-9.6:amd64 9.6~beta1-2.pgdg16.04+1 libpq5:amd64 9.6~beta1-2.pgdg16.04+1 postgresql-9.6:amd64 9.6~beta1-2.pgdg16.04+1 postgresql-client-common:amd64 174.pgdg16.04+1
Or if there is another solution to do cluster upgrade without older packages, I will be glad to hear it.



pgsql-admin by date:

Previous
From: Anonymous Anonymous
Date:
Subject: Need older (9.6~beta1-2.pgdg16.04+1) postgres beta packages
Next
From: Alex Malek
Date:
Subject: Re: problems using pg_start_backup/pg_stop_backup and pg_basebackup at same time