From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Allan Webber Subject: A plan for upgrading postgres? Date: Thu, 23 Jun 2016 10:13:03 -0500 Message-ID: <87vb10djls.fsf@dustycloud.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44463) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bG6Jd-0000UW-2B for guix-devel@gnu.org; Thu, 23 Jun 2016 11:13:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bG6Jb-0003gC-1L for guix-devel@gnu.org; Thu, 23 Jun 2016 11:13:12 -0400 Received: from dustycloud.org ([2600:3c02::f03c:91ff:feae:cb51]:39658) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bG6Ja-0003em-TN for guix-devel@gnu.org; Thu, 23 Jun 2016 11:13:10 -0400 Received: from oolong (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 674232663F for ; Thu, 23 Jun 2016 11:13:03 -0400 (EDT) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Heya everyone, I'm not sure anyone else is seriously running postgresql right now, but I've been using it for some test development, and eventually I intend to deploy to GNU Guix machines. I think to do this, we'll need to keep around the prior version of postgres. pg_upgrade requires it: https://www.postgresql.org/docs/9.4/static/pgupgrade.html I think the right approach will be to keep around the prior version, eg postgresql-9.4, as a first step. As a second step, it might be nice to have a package that's something like "postgres-upgrade-recent" which has all the shorthands for pointing at both the prior postgres binary and this one, and so hands the user a single script for running the upgrade. Just thought I'd write this out while thinking about it. Does it make sense? - Chris