Dmitry Yemanov wrote:

> 1) The LIST aggregate function doesn't return ranges anyway.
>

Yes, but speaking about architecture, result of LIST can be passed to IN
LIST, i.e., it's compatible.

> 2) Why a temp table requirement?
>

Ok, for LIST->IN LIST that is not required.
You can just don't use both.

> My question was not about IN LIST usage in general, I just question the
> point of it being considered a complement for the LIST function.
>

It's nice when more than one features can work together, and LIST and IN
LIST can.


Adriano