Re: Stability of queryid in minor versions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: David Rowley <dgrowleyml@gmail.com>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-15T01:19:34Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > On Mon, Apr 15, 2024 at 11:20:16AM +1200, David Rowley wrote: >> 1. We cannot change Node enums in minor versions >> 2. We're *unlikely* to add fields to Node types in minor versions, and >> if we did we'd likely be leaving them out of the jumble calc, plus it >> seems highly unlikely any new field we wedged into the padding would >> relate at all to the parsed query. > Since 16 these new fields would be added by default unless the node > attribute query_jumble_ignore is appended to it. They'd also be written/read by outfuncs/readfuncs, thereby breaking stored views/rules if the Node is one that can appear in a parsetree. So the bar to making such a change in a stable branch would be very high. regards, tom lane
Commits
-
Doc: document cases where queryid is stable
- 74a587a009d1 12.19 landed
- e4c76f5eca92 13.15 landed
- c6e229d5f76f 14.12 landed
- 38daca854adb 15.7 landed
- 0d8931c12aa9 16.3 landed
- 2d3389c28c5c 17.0 landed