pgsql: Portability hack for pg_global_prng_state.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Portability hack for pg_global_prng_state.
Date: 2021-11-29 05:04:58
Message-ID: E1mrYqY-0002sA-T2@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Portability hack for pg_global_prng_state.

PGDLLIMPORT is only appropriate for variables declared in the backend,
not when the variable is coming from a library included in frontend code.
(This isn't a particularly nice fix, but for now, use the same method
employed elsewhere.)

Discussion: https://postgr.es/m/E1mrWUD-000235-Hq@gemulon.postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/11b500072e42c214462b973b0b05f1c68992226b

Modified Files
--------------
src/include/common/pg_prng.h | 4 ++++
1 file changed, 4 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2021-11-29 14:58:12 Re: pgsql: Update high level vacuumlazy.c comments.
Previous Message Tom Lane 2021-11-29 04:57:58 Re: pgsql: Replace random(), pg_erand48(), etc with a better PRNG API and a