Re: Different result behavior when using ANY(ARRAY(SELECT)) and IN (SELECT)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Davide Jensen <d(dot)jensen(at)tecnoteca(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Different result behavior when using ANY(ARRAY(SELECT)) and IN (SELECT)
Date: 2020-11-09 15:10:30
Message-ID: 1974195.1604934630@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Davide Jensen <d(dot)jensen(at)tecnoteca(dot)com> writes:
> I'm encountering some problems in understanding the behavior of a query
> that uses an IN operator, the query i'm executing is the following:

> SELECT * FROM (
> SELECT _id,
> ROW_NUMBER() OVER () AS _rownumber

I think your problem is in the above, not anything later in the query.
ROW_NUMBER without any ordering specification is indeterminate.
If the query gets parallelized, it's no surprise that the selected rows
will be processed in varying order from one try to the next. Your
second phrasing of the query seems to be non-parallelizable, but the
row_number() result is still pretty indeterminate; it just doesn't
happen to have changed within your test run.

What is it you are expecting to get out of including a fictional
row number in the query result, anyway?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Gauthier 2020-11-09 15:24:04 database aliasing options ?
Previous Message Adrian Klaver 2020-11-09 14:29:25 Re: Database system was interrupted. Possible reasons for a database to suddenly stop accepting connections?