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

From Albe Laurenz
Subject Re: Parallel execution and prepared statements
Date
Msg-id A737B7A37273E048B164557ADEF4A58B53999D50@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Parallel execution and prepared statements  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas wrote:
>>    /* creates a parallel-enabled plan */
>>    PQprepare(conn, "pstmt", "SELECT id FROM l WHERE val = $1", 1, NULL);
>>    /* blows up with "cannot insert tuples during a parallel operation" */
>>    PQexec(conn, "CREATE TABLE bad(id) AS EXECUTE pstmt('abcd')");
> 
> Ouch.  I missed that.
> 
>> With Tobias' patch, this does not fail.
>>
>> I think we should either apply something like that patch or disable parallel
>> execution for prepared statements altogether and document that.
> 
> I agree.  I think probably the first option is better, but I might
> have to commit with one hand so I can hold my nose with the other.

Is there a better, more consistent approach for that?

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Mail thread references in commits
Next
From: Thomas Munro
Date:
Subject: Re: condition variables