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

From Marko Tiikkaja
Subject Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query
Date
Msg-id CAL9smLD+d+Bi1tvA8og5J+ZrW2E-yuyL1w4k2CdX3Fxb-vWDOQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Aug 14, 2018 at 2:50 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
This looks related, but I think this is a different issue.

Sure.
 
The real
reason for this case is that row_number is marked as parallel_safe
which seems to be wrong.  I think it should be marked as
parallel_unsafe.

Marking the function parallel safe doesn't seem wrong to me.  The non-parallel-safe part is that the input gets fed to it in different order in different workers.  And I don't really think that to be the function's fault.


.m

pgsql-bugs by date:

Previous
From: Sandeep Thakkar
Date:
Subject: Re: Issue
Next
From: Thom Brown
Date:
Subject: log_destination reload/restart doesn't stop file creation