From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Stability of queryid in minor versions |
Date: | 2024-04-15 02:09:13 |
Message-ID: | ZhyMSWlYzlUj9j7H@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 15, 2024 at 01:31:47PM +1200, David Rowley wrote:
> I think a soft guarantee in the docs for it being stable in minor
> versions would be ok then.
>
> I'm unsure if "Rule of thumb" is the correct way to convey that. We
> can't really write "We endeavour to", as who is "We". Maybe something
> like "Generally, it can be assumed that queryid is stable between all
> minor versions of a major version of ..., providing that <other
> reasons>".
It sounds to me that the term "best-effort" is adapted here? Like in
"The compatibility of query IDs is preserved across minor versions on
a best-effort basis. It is possible that the post-parse-analysis tree
changes across minor releases, impacting the value of queryid for the
same query run across two different minor versions.".
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-04-15 02:12:34 | Re: Fix out-of-bounds in the function GetCommandTagName |
Previous Message | David Rowley | 2024-04-15 02:03:02 | Re: Stability of queryid in minor versions |