From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <kgrittn@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Fixing target-column indirection in INSERT with multiple VALUES
Date: Wed, 27 Jul 2016 18:29:46 -0400
Message-ID: <22233.1469658586@sss.pgh.pa.us> (raw)
In-Reply-To: <CACjxUsPOj7iJuOaxtozcXL6d9dgAYhGnG=YKmUkWy8515Srd2Q@mail.gmail.com>
References: <9578.1469645245@sss.pgh.pa.us>
<CACjxUsPOj7iJuOaxtozcXL6d9dgAYhGnG=YKmUkWy8515Srd2Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Kevin Grittner <kgrittn@gmail.com> writes:
> On Wed, Jul 27, 2016 at 1:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> this would require an initdb because it changes the
>> representation of stored rules for cases like this,
> So pg_upgrade would not work at all for the version this goes into,
No, pg_upgrade wouldn't have a problem. The entire point of pg_upgrade
is to cope with system catalog changes.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: tgl@sss.pgh.pa.us, kgrittn@gmail.com
Subject: Re: Fixing target-column indirection in INSERT with multiple VALUES
In-Reply-To: <22233.1469658586@sss.pgh.pa.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