Re: [COMMITTERS] pgsql: Mark pg_start_backup and pg_stop_backup as parallel-restricted.

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [COMMITTERS] pgsql: Mark pg_start_backup and pg_stop_backup as parallel-restricted.
Дата
Msg-id CA+TgmoZLTB+1V1qZV6+E3R0BmHkBVReR9KP=tynUVNySgUhWkw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Mark pg_start_backup and pg_stop_backup as parallel-restricted.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
On Mon, Mar 6, 2017 at 3:23 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Yes, I think it's rather silly not to do so.  We have made comparable
> backpatched fixes multiple times in the past.  What is worth discussing is
> whether there are *additional* things we ought to do in 9.6 to prevent
> misbehavior in installations initdb'd pre-9.6.3.
>
> If there's a cheap way of testing "AmInParallelWorker", I'd be in favor of
> adding a quick-n-dirty test and ereport(ERROR) to these functions in the
> 9.6 branch, so that at least you get a clean error and not some weird
> misbehavior.  Not sure if there's anything more we can do than that.

Sounds like you want IsParallelWorker().

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


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: [COMMITTERS] pgsql: Avoid dangling pointer to relation name in RLS code path inDoCo
Следующее
От: Stephen Frost
Дата:
Сообщение: [COMMITTERS] pgsql: pg_upgrade: Fix large object COMMENTS, SECURITY LABELS