Re: Improve handling of pg_stat_statements handling of bind "IN" variables

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:34:00
Message-ID: CAM-w4HNZCUyaNT0OwcYQ7PRVpXP6tosBD0dmmKskDdfVQGXkEQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat., Jun. 15, 2019, 8:30 p.m. Greg Stark, <stark(at)mit(dot)edu> wrote:

>
>
> So what would this do for someone who explicitly writes:
>
> WHERE col = ANY ?
>
> and pass an array?
>

Actually thinking about this for two more seconds the question is what it
would do with a query like

WHERE col = ANY '1,2,3'::integer[]

Or

WHERE col = ANY ARRAY[1,2,3]

Whichever the language binding that is failing to do parameterized queries
is doing to emulate them.

>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2019-06-16 01:04:04 The flinfo->fn_extra question, from me this time.
Previous Message Greg Stark 2019-06-16 00:30:06 Re: Improve handling of pg_stat_statements handling of bind "IN" variables