From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Remove Value node struct |
Date: | 2021-08-25 13:19:49 |
Message-ID: | 5ba6bc5b-3f95-04f2-2419-f8ddb4c046fb@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
While trying to refactor the node support in various ways, the Value
node is always annoying.
The Value node struct is a weird construct. It is its own node type,
but most of the time, it actually has a node type of Integer, Float,
String, or BitString. As a consequence, the struct name and the node
type don't match most of the time, and so it has to be treated
specially a lot. There doesn't seem to be any value in the special
construct. There is very little code that wants to accept all Value
variants but nothing else (and even if it did, this doesn't provide
any convenient way to check it), and most code wants either just one
particular node type (usually String), or it accepts a broader set of
node types besides just Value.
This change removes the Value struct and node type and replaces them
by separate Integer, Float, String, and BitString node types that are
proper node types and structs of their own and behave mostly like
normal node types.
Also, this removes the T_Null node tag, which was previously also a
possible variant of Value but wasn't actually used outside of the
Value contained in A_Const. Replace that by an isnull field in
A_Const.
Attachment | Content-Type | Size |
---|---|---|
0001-Remove-useless-casts.patch | text/plain | 9.2 KB |
0002-Remove-Value-node-struct.patch | text/plain | 55.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2021-08-25 13:21:36 | Re: [PATCH] document |
Previous Message | Amit Kapila | 2021-08-25 13:17:05 | Re: Failure of subscription tests with topminnow |