Re: [COMMITTERS] pgsql: Improve access to parallel queryfrom procedural languages. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Improve access to parallel queryfrom procedural languages.
Date
Msg-id CA+Tgmoa0JQ_P-6yooNTMfgXDSE04goj_pEP5qPioZ3qobCBuvA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Improve access to parallel queryfrom procedural languages.  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
List pgsql-hackers
On Mon, Mar 27, 2017 at 11:57 PM, Rafia Sabih
<rafia.sabih@enterprisedb.com> wrote:
> On Mon, Mar 27, 2017 at 5:54 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>> If it's just that they are relying on unsynchronized global variables,
>> then it's sufficient to mark them parallel-restricted ('r').  Do we
>> really need to go all the way to parallel-unsafe ('u')?
>>
> Done.

OK, but don't pg_event_trigger_dropped_objects and
pg_event_trigger_ddl_commands need the same treatment?

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



pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Monitoring roles patch
Next
From: Peter Eisentraut
Date:
Subject: Re: Monitoring roles patch