Re: pgsql: Replace random(), pg_erand48(), etc with a better PRNG API and a

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Replace random(), pg_erand48(), etc with a better PRNG API and a
Дата
Msg-id 1140657.1638161878@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Replace random(), pg_erand48(), etc with a better PRNG API and a  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
Дерево обсуждения 
I wrote:
> ... If so, we could perhaps
> fix it by doing

> #ifdef FRONTEND
> extern pg_prng_state pg_global_prng_state;
> #else
> extern PGDLLIMPORT pg_prng_state pg_global_prng_state;
> #endif

Ah, I now see the same hack being used in keywords.h and pg_bitutils.h,
so I'll go do that.  (Maybe we should invent a variant of PGDLLIMPORT
that can make this happen without as much code duplication?)

            regards, tom lane

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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: pgsql: Centralize timestamp computation of control file on updates
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Portability hack for pg_global_prng_state.