| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: queryId constant squashing does not support prepared statements |
| Date: | 2025-05-02 12:56:56 |
| Message-ID: | 202505021256.4yaa24s3sytm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-May-02, Michael Paquier wrote:
> That depends. If we conclude that tracking this information through
> the parser based on the start and end positions in a query string
> for a set of values is more relevant, then we would be redesigning the
> facility from the ground, so the old approach would not be really
> relevant..
I disagree that a revert is warranted for this reason. If you want to
change the implementation later, that's fine, as long as the user
interface doesn't change.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Doing what he did amounts to sticking his fingers under the hood of the
implementation; if he gets his fingers burnt, it's his problem." (Tom Lane)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2025-05-02 13:00:29 | Small fixes needed by high-availability tools |
| Previous Message | Robert Haas | 2025-05-02 12:04:42 | Re: fixing CREATEROLE |