Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Andreas Seltenreich <seltenreich(at)gmx(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted
Date: 2016-06-11 11:27:44
Message-ID: CAA4eK1+P5ckWhn3-N7Ecyi+P3+Zdgi=8=j8+OAg+OzqFQ16Acg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Jun 11, 2016 at 2:07 PM, Andreas Seltenreich <seltenreich(at)gmx(dot)de>
wrote:
>
> Amit Kapila writes:
>
> > I have moved it to CLOSE_WAIT state because we have derived our
> > queries to reproduce the problem based on original report[1]. If next
> > run of sqlsmith doesn't show any problem in this context then we will
> > move it to resolved.
>
> I don't have access to my testing horse power this weekend so I can
> report on tuesday at the earliest. Unless someone else feels like
> running sqlsmith…
>

No issues and many thanks for testing.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Kevin Grittner 2016-06-11 15:29:54 Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <
Previous Message Andreas Seltenreich 2016-06-11 08:37:00 Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-06-11 12:22:27 Re: Confusing recovery message when target not hit
Previous Message Andreas Seltenreich 2016-06-11 08:37:00 Re: [COMMITTERS] pgsql: Don't generate parallel paths for rels with parallel-restricted