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

help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Transactional sequence stuff breaks pg_upgrade
Date: Tue, 13 Jun 2017 13:07:59 -0400
Message-ID: <20170613170759.GF13873@momjian.us> (raw)
In-Reply-To: <CA+TgmobeqQPqwbskQ2ZPJ-AEfzZgyteKUZV_gn1g0VB_VZfMag@mail.gmail.com>
References: <19785.1497215827@sss.pgh.pa.us>
	<9761.1497225808@sss.pgh.pa.us>
	<20170612210221.vz2u373tcwu3g624@alap3.anarazel.de>
	<23291.1497302014@sss.pgh.pa.us>
	<20170612212517.j3xe6am7hlztl6fw@alap3.anarazel.de>
	<CA+TgmobZhwAOwudbXaEB0WQ8C-qL9kPCGDUsu3EMY_VhDDY7zg@mail.gmail.com>
	<32233.1497361079@sss.pgh.pa.us>
	<CA+TgmobeqQPqwbskQ2ZPJ-AEfzZgyteKUZV_gn1g0VB_VZfMag@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Tue, Jun 13, 2017 at 11:14:02AM -0400, Robert Haas wrote:
> Also, I think that if we did it that way, it would be significantly
> harder to debug.  Right now, if something goes boom, you can look at
> the old and new clusters and figure out what doesn't match, but if
> pg_upgrade renumbered everything, you would no longer be able to do
> that, or at least not easily.

FYI, pg_upgrade is designed to go boom if something doesn't look right
because it can't anticipate what changes might be made to Postgres in
the future.

boom == feature!

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (14+ messages)

Message-ID: <20170613170759.GF13873@momjian.us>
Permalink:  ../20170613170759.GF13873@momjian.us/
Also on:    postgresql.org/message-id/20170613170759.GF13873@momjian.us

 · 

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: bruce@momjian.us, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, peter.eisentraut@2ndquadrant.com
  Subject: Re: Transactional sequence stuff breaks pg_upgrade
  In-Reply-To: <20170613170759.GF13873@momjian.us>

* 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