Re: parallelize queries containing initplans

From: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: parallelize queries containing initplans
Date: 2017-10-18 08:36:04
Message-ID: f17e7e28-7508-3494-6409-0e61c01ca819@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/11/2017 12:42 PM, tushar wrote:
> On 10/09/2017 03:26 PM, Amit Kapila wrote:
>> I have reverted the check
>> in the attached patch.
>
> I have applied this patch against PG HEAD and run sqlsmith and
> analyzed results . didn't find any specific failures against this patch.
>
I did some testing of  this feature and written few testcases . PFA the
sql  file(along with the expected .out file) .

--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company

Attachment Content-Type Size
pip.sql application/sql 9.2 KB
pip.out text/plain 109.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-10-18 08:53:23 Re: [COMMITTERS] pgsql: Implement table partitioning.
Previous Message Masahiko Sawada 2017-10-18 07:16:55 Re: pgbench: Skipping the creating primary keys after initialization