| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 07:24:15 |
| Message-ID: | bxthy72s3qxuvj4ffcpcje3cgqvir6hjlbrwf62wxxka7xkkal@d4vgwirvcbji |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Fri, May 02, 2025 at 04:18:37PM GMT, Michael Paquier wrote:
> On Fri, May 02, 2025 at 09:13:39AM +0200, Dmitry Dolgov wrote:
> > Squashing constants was ment to be a first step towards doing the same
> > for other types of queries (params, rte_values), reverting it to
> > implement everything at once makes very little sense to me.
>
> 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..
If I understand you correctly, changing the way how element list is
identified is not going to address the question whether or not to squash
parameters, right?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nisha Moond | 2025-05-02 07:27:25 | Re: Fix slot synchronization with two_phase decoding enabled |
| Previous Message | Michael Paquier | 2025-05-02 07:18:37 | Re: queryId constant squashing does not support prepared statements |