pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Christoph Berg <myon@debian.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, Tomasz Szypowski <tomasz.szypowski@gmail.com>
Subject: Re: pg_upgrade version checking questions
Date: Fri, 22 Mar 2019 10:45:40 +0100
Message-ID: <20190322094539.GB32388@msg.df7cb.de> (raw)
In-Reply-To: <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>
References: <9328.1552952117@sss.pgh.pa.us>
	<b659c1df-c37a-52da-da7f-e0659c34c92a@2ndquadrant.com>
	<13426.1553010710@sss.pgh.pa.us>
	<57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>

Re: Peter Eisentraut 2019-03-22 <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>
> I'm still in favor of defaulting --new-bindir appropriately.  It seems
> silly not to.  We know where the directory is, we don't have to ask anyone.

Fwiw I've been wondering why I have to pass that option every time
I've been using pg_upgrade. +1 on making it optional/redundant.

Christoph

view thread (25+ messages)  latest in thread

Message-ID: <20190322094539.GB32388@msg.df7cb.de>
Permalink:  ../20190322094539.GB32388@msg.df7cb.de/
Also on:    postgresql.org/message-id/20190322094539.GB32388@msg.df7cb.de

copy link · copy postgr.es

reply

Reply instructions:

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

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: myon@debian.org, peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, tomasz.szypowski@gmail.com
  Subject: Re: pg_upgrade version checking questions
  In-Reply-To: <20190322094539.GB32388@msg.df7cb.de>

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

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox