Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry members enrname and enrtup - Mailing list pgsql-committers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry members enrname and enrtup
Date
Msg-id 31330.1497536276@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry membersenrname and enrtup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry membersenrname and enrtup  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-committers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Jun 14, 2017 at 4:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> This really should have involved a catversion bump.  But we just
>> had one earlier today, so in practice it might not matter.

> Oh, because of stored rules using the old RangeTblEntry serialization
> format?  Sorry, I totally missed that.

Yeah, exactly.  In practice I'm not sure a stored rule/view could contain
an RTE_NAMEDTUPLESTORE RangeTblEntry, but if it did, there'd be a problem.

            regards, tom lane


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix document bug regarding read only transactions.
Next
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry membersenrname and enrtup