| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Pavel Trukhanov <pavel(dot)trukhanov(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improve handling of pg_stat_statements handling of bind "IN" variables |
| Date: | 2019-06-16 00:30:06 |
| Message-ID: | CAM-w4HNUdQDpXG6BdTmS-NTTgZA5RoZpuamuNkftv8reF1N7jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat., Jun. 15, 2019, 12:29 p.m. Pavel Trukhanov, <
pavel(dot)trukhanov(at)gmail(dot)com> wrote:
>
> So I don't think there's actually enough benefit to split those two apart.
>
> Now I want to do this: just add a meta info (basically a bool field)
> to the ArrayExpr struct, so on later stages we could tell if that's an
> ArrayExpr of an ARRAY or of an IN list. Plus to add ignoring updating
> Jumble for expression subtree within IN-list array.
>
> If that approach doesn't seem too bad to anyone, I would like to go
> forward and submit a patch – it seems pretty straightforward to
> implement that.
>
So what would this do for someone who explicitly writes:
WHERE col = ANY ?
and pass an array?
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2019-06-16 00:34:00 | Re: Improve handling of pg_stat_statements handling of bind "IN" variables |
| Previous Message | Tomas Vondra | 2019-06-15 23:24:28 | Re: Multivariate MCV stats can leak data to unprivileged users |