Re: executor relation handling - Mailing list pgsql-hackers

From Robert Haas
Subject Re: executor relation handling
Date
Msg-id CA+TgmoZCK450=v4vWsOEutCc0dQnBp5Lx09eSco8L+25ANs3nA@mail.gmail.com
Whole thread Raw
In response to Re: executor relation handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Oct 9, 2018 at 2:35 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > That last part could *easily* change in a future release.  We've
> > already started to allow CTAS with parallel query, and there have
> > already been multiple people wanting to allow more.  It would be a
> > shame if we threw up additional obstacles in the way of that...
>
> I hardly think that this is the most serious issue in the way of
> doing non-read-only things in parallel workers.

My concern, as I said, is about adding new obstacles.

> In any case, a parallel worker would surely have to open any
> relations it is going to fire triggers for.  If it gets the correct
> lock when it does that, all is well.  If not, the Assert in
> relation_open will complain.

Well, in that case, no issues.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: background worker shudown (was Re: [HACKERS] Why does logicalreplication launcher exit with exit code 1?)
Next
From: Thomas Munro
Date:
Subject: Re: DSM segment handle generation in background workers