diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2024-03-07 11:50:24 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2024-03-07 12:13:09 +0100 |
| commit | 6d470211e54f7a617783b99b27c9d8056a890a57 (patch) | |
| tree | 09101a6e43c2cfe1b5a423f113ce0db05e1abe85 /src/backend/nodes/queryjumblefuncs.c | |
| parent | 1f1d73a8b83fb6de929af36eb9d3cd590875daf5 (diff) | |
| download | postgresql-6d470211e54f7a617783b99b27c9d8056a890a57.tar.gz postgresql-6d470211e54f7a617783b99b27c9d8056a890a57.zip | |
Fix description and grouping of RangeTblEntry.inh
The inh field of RangeTblEntry was doubly confusingly documented.
Some parts of the code insisted that it was only valid for
RTE_RELATION entries, other parts said the field was valid for all
entries. Neither was quite correct. More correctly, the field is
valid for RTE_RELATION entries but is also used in the planner for
RTE_SUBQUERY entries. So it makes more sense to group it with other
fields that are primarily for RTE_RELATION but borrowed by
RTE_SUBQUERY. (The exact position was chosen so that it is next to
relkind for better struct packing, and next to relid, since relid and
inh are sort of the input fields and the others are filled in later.)
Also add documentation for the planner's use at the struct definition.
Discussion: https://www.postgresql.org/message-id/6c1fbccc-85c8-40d3-b08b-4f47f2093711@eisentraut.org
Diffstat (limited to 'src/backend/nodes/queryjumblefuncs.c')
| -rw-r--r-- | src/backend/nodes/queryjumblefuncs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/nodes/queryjumblefuncs.c b/src/backend/nodes/queryjumblefuncs.c index 426112fa37b..2c116c87288 100644 --- a/src/backend/nodes/queryjumblefuncs.c +++ b/src/backend/nodes/queryjumblefuncs.c @@ -364,8 +364,8 @@ _jumbleRangeTblEntry(JumbleState *jstate, Node *node) { case RTE_RELATION: JUMBLE_FIELD(relid); - JUMBLE_NODE(tablesample); JUMBLE_FIELD(inh); + JUMBLE_NODE(tablesample); break; case RTE_SUBQUERY: JUMBLE_NODE(subquery); |