Re: pgsql: Fix problems related to RangeTblEntry members enrname and enrtup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix problems related to RangeTblEntry members enrname and enrtup
Date: 2017-06-15 14:17:56
Message-ID: 31330.1497536276@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jun 14, 2017 at 4:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-06-15 14:47:54 Re: pgsql: Fix problems related to RangeTblEntry members enrname and enrtup
Previous Message Tom Lane 2017-06-15 14:13:00 Re: pgsql: Fix document bug regarding read only transactions.