Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query
Date
Msg-id 21038.1534181205@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query  (Marko Tiikkaja <marko@joh.to>)
Responses Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-bugs
Marko Tiikkaja <marko@joh.to> writes:
> On Mon, Aug 13, 2018 at 7:35 PM, Andres Freund <andres@anarazel.de> wrote:
>> Well, the subselect with thelimit going to return different results from
>> run to run. Unless you add an ORDER BY there's no guaranteed order in
>> which tuples are returned.  So I don't think it's surprising that you're
>> getting results that differ between runs.

> While this is true, that's missing the point.

Yeah, I agree.  I think probably what's happening is that the sub-select
is getting pushed down to the parallel workers and they are not all
computing the same set of sub-select results, leading to inconsistent
answers at the top level.

Likely, we need to treat the presence of a LIMIT/OFFSET in a sub-select
as making it parallel-unsafe, for exactly the reason that that makes
its results non-deterministic.

            regards, tom lane


pgsql-bugs by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query
Next
From: Pavel Stehule
Date:
Subject: Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query