Re: T_PrivGrantee is left in NodeTag - Mailing list pgsql-hackers

From Kyotaro HORIGUCHI
Subject Re: T_PrivGrantee is left in NodeTag
Date
Msg-id 20150916.160805.66837154.horiguchi.kyotaro@lab.ntt.co.jp
Whole thread Raw
In response to T_PrivGrantee is left in NodeTag  (Yugo Nagata <nagata@sraoss.co.jp>)
Responses Re: T_PrivGrantee is left in NodeTag  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi, thank you for pointing it out.

At Wed, 16 Sep 2015 14:02:30 +0900, Yugo Nagata <nagata@sraoss.co.jp> wrote in
<20150916140230.a232426c.nagata@sraoss.co.jp>
> I found that codes about T_PrivGrantee was removed
> by the following commit;
> http://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=31eae6028eca4365e7165f5f33fee1ed0486aee0
> 
> but T_PrivGrantee is left in NodeTag in src/include/nodes/nodes.h.
> 
> Is it intended?

I simply forgot to remove it.

The comment for NodeTag says that,

====* Note that the numbers of the node tags are not contiguous. We left holes* here so that we can add more tags
withoutchanging the existing enum's.* (Since node tag numbers never exist outside backend memory, there's no* real harm
inrenumbering, it just costs a full rebuild ...)
 
====

However, I think it'd be better to be removed.

Thoughts? The attached patch simply removes it.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: src/test/ssl broken on HEAD
Next
From: Craig Ringer
Date:
Subject: Reliance on undefined behaviour in << operator