Re: Revisiting pg_stat_statements and IN() (Was: Re: pg_stat_statements fingerprinting logic and ArrayExpr)

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Revisiting pg_stat_statements and IN() (Was: Re: pg_stat_statements fingerprinting logic and ArrayExpr)
Date: 2015-11-25 01:46:04
Message-ID: CAM3SWZQ3R-t2WDBiFx5TFme4eKKmT0safCoB1oaA3e3UCdfr0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 24, 2015 at 5:39 PM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> Another not-uncommon case is IN ( '1', '2', ... , '2342' ); in other words,
> treating an integer as text. A lot of frameworks like to do that and just
> push the problem onto the database. I'm not sure what pg_stat_statements
> would ultimately see in that case..

They do?

postgres=# select 5::int4 in ('5');
?column?
──────────
t
(1 row)

postgres=# select 5::int4 in ('5a');
ERROR: 22P02: invalid input syntax for integer: "5a"
LINE 1: select 5::int4 in ('5a');
^
--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2015-11-25 01:47:33 Re: New email address
Previous Message Greg Stark 2015-11-25 01:42:13 Re: Using quicksort for every external sort run