mirror of
https://github.com/postgres/postgres.git
synced 2025-07-08 11:42:09 +03:00
Improve field order in RangeTblEntry
When perminfoindex was added, it was just added at the end of the block. It would make sense to keep it closer to more related fields. In passing, also add an inline comment, like the other fields have. (Other field reorderings and documentation improvements in RangeTblEntry are being discussed, but it's better not to mix them together.) Discussion: https://www.postgresql.org/message-id/flat/6c1fbccc-85c8-40d3-b08b-4f47f2093711%40eisentraut.org
This commit is contained in:
@ -359,8 +359,8 @@ _readRangeTblEntry(void)
|
||||
READ_OID_FIELD(relid);
|
||||
READ_CHAR_FIELD(relkind);
|
||||
READ_INT_FIELD(rellockmode);
|
||||
READ_NODE_FIELD(tablesample);
|
||||
READ_UINT_FIELD(perminfoindex);
|
||||
READ_NODE_FIELD(tablesample);
|
||||
break;
|
||||
case RTE_SUBQUERY:
|
||||
READ_NODE_FIELD(subquery);
|
||||
|
Reference in New Issue
Block a user