From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Improve documentation of struct ParseState. |
Date: | 2017-01-07 21:02:34 |
Message-ID: | E1cPy8I-0007KK-FN@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Improve documentation of struct ParseState.
I got annoyed about how some fields of ParseState were documented in the
struct's block comment and some weren't; not all of the latter are trivial.
Fix that. Also reorder a couple of fields that seem to have been placed
rather randomly, or maybe with an idea of avoiding padding space; but there
are never so many ParseStates in existence at one time that we ought to
value pad space over readability.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/3c40594e6eeabb3a8ad22aee93de3a19c41efdc2
Modified Files
--------------
src/include/parser/parse_node.h | 44 ++++++++++++++++++++++++++++++++++++-----
1 file changed, 39 insertions(+), 5 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2017-01-09 15:05:11 | pgsql: Use an enum instead of two bools to indicate wal inclusion in ba |
Previous Message | Stephen Frost | 2017-01-06 21:29:48 | pgsql: Add basic pg_dumpall/pg_restore TAP tests |