Re: pg_stat_statements and "IN" conditions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_stat_statements and "IN" conditions
Date
Msg-id 2420105.1675612952@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_stat_statements and "IN" conditions  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: pg_stat_statements and "IN" conditions
List pgsql-hackers
Dmitry Dolgov <9erthalion6@gmail.com> writes:
> I'm thinking about this in the following way: the core jumbling logic is
> responsible for deriving locations based on the input expressions; in
> the case of merging we produce less locations; pgss have to represent
> the result only using locations and has to be able to differentiate
> simple locations and locations after merging.

Uh ... why?  ISTM you're just going to elide all inside the IN,
so why do you need more than a start and stop position?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Compression dictionaries for JSONB
Next
From: Tom Lane
Date:
Subject: Re: File descriptors in exec'd subprocesses