Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query |
| Дата | |
| Msg-id | 21038.1534181205@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query (Marko Tiikkaja <marko@joh.to>) |
| Ответы |
Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query
Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query |
| Список | 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 по дате отправления: