Re: post-freeze damage control
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2024-04-09T21:05:02Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
revert: Transform OR clauses to ANY expression
- ff9f72c68f67 17.0 landed
-
Fix incorrect calculation in BlockRefTableEntryGetBlocks.
- 55a5ee30cd65 17.0 cited
Alexander Korotkov <aekorotkov@gmail.com> writes: > On Tue, Apr 9, 2024 at 11:37 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> What exactly is the point of having a NodeTag in the struct though? >> If you don't need it to be a valid Node, that seems pointless and >> confusing. We certainly have plenty of other lists that contain >> plain structs without tags, so I don't buy that the List >> infrastructure is making you do that. > This code mixes Expr's and hash entries in the single list. The point > of having a NodeTag in the struct is the ability to distinguish them > later. If you're doing that, it really really ought to be a proper Node. If nothing else, that would aid debugging by allowing the list to be pprint'ed. regards, tom lane