Re: Parallel execution and prepared statements - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parallel execution and prepared statements
Date
Msg-id CAA4eK1LTm5-tbHszwYqcqAF09fY8avgU=3k-_dGOXrxae6pihw@mail.gmail.com
Whole thread Raw
In response to Re: Parallel execution and prepared statements  (Albe Laurenz <laurenz.albe@wien.gv.at>)
Responses Re: Parallel execution and prepared statements  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Tue, Nov 29, 2016 at 4:40 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
> Amit Kapila wrote:
>>> But with Tobias' complete patch "make installcheck-world" succeeds.
>>
>> Okay.  I have looked into patch proposed and found that it will
>> resolve the regression test problem (Create Table .. AS Execute).  I
>> think it is slightly prone to breakage if tomorrow we implement usage
>> of EXECUTE with statements other Create Table (like Copy).  Have you
>> registered this patch in CF to avoid loosing track?
>>
>> We have two patches (one proposed in this thread and one proposed by
>> me earlier [1]) and both solves the regression test failure.  Unless
>> there is some better approach, I think we can go with one of these.
>
> Tobias did that here: https://commitfest.postgresql.org/12/890/
>
> He added your patch as well.
>

Okay, Thanks.

Robert, do you have any better ideas for this problem?

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



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Declarative partitioning - another take
Next
From: Simon Riggs
Date:
Subject: XactLockTableWait doesn't set wait_event correctly