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

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry membersenrname and enrtup
Date
Msg-id CA+TgmoZxRDFtXYPZhnd81-rPk51-4mSkuVaebWN7m76LddTpHA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry members enrname and enrtup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Fix problems related to RangeTblEntry members enrname and enrtup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Wed, Jun 14, 2017 at 4:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <rhaas@postgresql.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


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: [COMMITTERS] pgsql: Fix typo in code comment
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Fix document bug regarding read only transactions.