Re: [HACKERS] SERIALIZABLE with parallel query

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] SERIALIZABLE with parallel query
Дата
Msg-id CA+Tgmoa0y20_49a+7b_CMoZv79Xz-sVjuC=Dht0mXf9Y+UfvsA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] SERIALIZABLE with parallel query  (Thomas Munro <thomas.munro@enterprisedb.com>)
Ответы Re: [HACKERS] SERIALIZABLE with parallel query  (Thomas Munro <thomas.munro@enterprisedb.com>)
Список pgsql-hackers
On Wed, Feb 28, 2018 at 11:35 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Mon, Feb 26, 2018 at 6:37 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> I've now broken it into two patches.
>
> Rebased.

+SerializableXactHandle
+ShareSerializableXact(void)
+{
+    Assert(!IsParallelWorker());
+
+    return MySerializableXact;
+}

Uh, how's that OK?  There's no rule that you can't create a
ParallelContext in a worker.  Parallel query currently doesn't, so it
probably won't happen, but burying an assertion to that effect in the
predicate locking code doesn't seem nice.

Is "sxact" really the best (i.e. clearest) name we can come up with
for the lock tranche?

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


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

Предыдущее
От: David Fetter
Дата:
Сообщение: Re: csv format for psql
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: public schema default ACL