Re: Parallel safety of CURRENT_* family

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Parallel safety of CURRENT_* family
Дата
Msg-id 8557.1480619880@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Parallel safety of CURRENT_* family  (<5bih4k+4jfl6m39j23k@guerrillamail.com>)
Ответы Re: Parallel safety of CURRENT_* family  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
<5bih4k+4jfl6m39j23k@guerrillamail.com> writes:
> How should I mark a function which calls CURRENT_DATE? Parallel safe or parallel restricted?

> pg_proc shows that now() is marked as restricted, but transaction_timestamp() is marked as safe.

That's certainly silly, because they're equivalent.  I should think
they're both safe.  Robert?
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pgbench - allow backslash continuations in \set expressions
Следующее
От: Robert Haas
Дата:
Сообщение: Re: Broken SSL tests in master