| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Andrew Fletcher <andy(at)prestigedigital(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <marko(at)joh(dot)to>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query |
| Date: | 2018-08-16 06:59:26 |
| Message-ID: | CAA4eK1LBJ1qurk6sNg5zyTo+C24BNqg_hpg_q6BMeb_Zya0QVw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 16, 2018 at 11:47 AM, Andrew Fletcher
<andy(at)prestigedigital(dot)com> wrote:
>> (a) Consider the presence of a LIMIT/OFFSET in a sub-select as making
>> it parallel-unsafe.
>
>
> Presence of a LIMIT/OFFSET in a sub-select without an ORDER BY?
>
Yes, I wanted to do that, but Tom doesn't seem to like that especially
for back-branches. Let me try to prepare a patch and then we can see
based on the complexity of fix.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | DEGLAVE Remi | 2018-08-16 07:05:53 | RE: [PG_UPGRADE] 9.6 to 10.5 |
| Previous Message | Andrew Fletcher | 2018-08-16 06:17:53 | Re: BUG #15324: Non-deterministic behaviour from parallelised sub-query |