| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [HACKERS] Preserving param location |
| Date: | 2021-06-27 03:35:39 |
| Message-ID: | 20210627033539.53gfcixzd3u5yl4j@nol |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jun 27, 2021 at 11:31:53AM +0800, Julien Rouhaud wrote:
> On Sat, Mar 11, 2017 at 11:09:32PM +0100, Julien Rouhaud wrote:
> >
> > When a query contains parameters, the original param node contains the token
> > location. However, this information is lost when the Const node is generated,
> > this one will only contain position -1 (unknown).
> >
> > FWIW, we do have a use case for this (custom extension that tracks quals
> > statistics, which among other thing is used to regenerate query string from a
> > pgss normalized query, thus needing the original param location).
>
> rebased v2.
This time with the patch.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Preserve-param-location-when-generating-a-const-n.patch | text/x-diff | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-06-27 04:11:38 | Deparsing rewritten query |
| Previous Message | Julien Rouhaud | 2021-06-27 03:31:53 | Re: [HACKERS] Preserving param location |