Re: Fixing target-column indirection in INSERT with multiple VALUES - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Fixing target-column indirection in INSERT with multiple VALUES
Date
Msg-id CACjxUsPOj7iJuOaxtozcXL6d9dgAYhGnG=YKmUkWy8515Srd2Q@mail.gmail.com
Whole thread Raw
In response to Fixing target-column indirection in INSERT with multiple VALUES  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing target-column indirection in INSERT with multiple VALUES  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jul 27, 2016 at 1:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I looked into the problem reported in bug #14265,

> attached is a proposed patch that fixes this bug

> 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,
or do you see us testing for such cases and allowing pg_upgrade if
none are found?  Or do you see a way to allow pg_upgrade in the
face of such stored rules?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Why we lost Uber as a user
Next
From: Tom Lane
Date:
Subject: Re: Fixing target-column indirection in INSERT with multiple VALUES