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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:10:10
Message-ID: CA+TgmoZxRDFtXYPZhnd81-rPk51-4mSkuVaebWN7m76LddTpHA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Jun 14, 2017 at 4:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
>> Fix problems related to RangeTblEntry members enrname and enrtuples.
>> Commit 18ce3a4ab22d2984f8540ab480979c851dae5338 failed to update
>> the comments in parsenodes.h for the new members, and made only
>> incomplete updates to src/backend/nodes
>
> 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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-06-15 14:13:00 Re: pgsql: Fix document bug regarding read only transactions.
Previous Message Peter Eisentraut 2017-06-15 13:45:30 pgsql: Fix typo in code comment