From: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(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 03:57:11 |
Message-ID: | CAOGQiiNLzuNHX-0Ac=2gSVnpGYOgYLsntgZ8VM9zxnd-8cBEgQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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.
--
Regards,
Rafia Sabih
EnterpriseDB: http://www.enterprisedb.com/
Attachment | Content-Type | Size |
---|---|---|
system_defined_fn_update_v2.patch | application/octet-stream | 3.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2017-03-28 09:23:57 | Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic |
Previous Message | Tom Lane | 2017-03-28 00:58:53 | Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2017-03-28 04:21:13 | Re: crashes due to setting max_parallel_workers=0 |
Previous Message | Thomas Munro | 2017-03-28 03:47:59 | Re: O(1) DSM handle operations |