Re: random() (was Re: New GUC to sample log queries)

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: random() (was Re: New GUC to sample log queries)
Дата
Msg-id 20181227020433.GH2106@paquier.xyz
обсуждение исходный текст
Ответ на Re: random() (was Re: New GUC to sample log queries)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Wed, Dec 26, 2018 at 08:46:25PM -0500, Tom Lane wrote:
> One thing I was wondering is if we should try to enforce a policy
> like this by putting, say,
>
> #define random() pg_random()
>
> into port.h or so.  That would have the advantages of not having to touch
> any existing calls and not having to worry too much about future patches
> breaking the policy.  On the other hand, it's conceivable that third-party
> extensions might get annoyed with us for hijacking a libc function.
> Thoughts?

Not much a fan of that for random() to be honest as we are talking
about 15 callers in the backend code and enforcing a call of in a
low-level library..
--
Michael

Вложения

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

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: GIN predicate locking slows down valgrind isolationtests tremendously
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pgsql: Fix failure to check for open() or fsync() failures.