| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Improve access to parallel query from procedural languages. |
| Date: | 2017-03-28 15:35:15 |
| Message-ID: | CA+Tgmoa0JQ_P-6yooNTMfgXDSE04goj_pEP5qPioZ3qobCBuvA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Mar 27, 2017 at 11:57 PM, Rafia Sabih
<rafia(dot)sabih(at)enterprisedb(dot)com> wrote:
> On Mon, Mar 27, 2017 at 5:54 PM, Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2017-03-28 15:59:33 | pgsql: Altering default privileges on schemas |
| Previous Message | Peter Eisentraut | 2017-03-28 15:16:22 | pgsql: dblink: Fix error reporting |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-28 15:37:42 | Re: Monitoring roles patch |
| Previous Message | Dave Page | 2017-03-28 15:34:00 | Re: Monitoring roles patch |