unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel@gnu.org
Subject: Re: A plan for upgrading postgres?
Date: Fri, 24 Jun 2016 14:48:52 +0200	[thread overview]
Message-ID: <87vb0y4urv.fsf@gnu.org> (raw)
In-Reply-To: <87vb10djls.fsf@dustycloud.org> (Christopher Allan Webber's message of "Thu, 23 Jun 2016 10:13:03 -0500")

Hi, Chris!

Christopher Allan Webber <cwebber@dustycloud.org> skribis:

> 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.

According to the description, we must keep a package of the previous
major version so that we can pass it to ‘pg_upgrade -b’.

I agree that it would be convenient to have a ‘postgresql-upgrade’
package that would contain a program roughly doing:

  NEW/bin/pg_upgrade -b OLD/bin -B NEW/bin "$@"

(Disclaimer: I have little experience with PG!)

Ludo’.

      reply	other threads:[~2016-06-24 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 15:13 A plan for upgrading postgres? Christopher Allan Webber
2016-06-24 12:48 ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vb0y4urv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cwebber@dustycloud.org \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).