Re: Move OpenSSL random under USE_OPENSSL_RANDOM

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Move OpenSSL random under USE_OPENSSL_RANDOM
Date: 2020-11-19 20:49:05
Message-ID: CABUevEyG_+1OGM8Jegdw0ZZz5ZEV=qJ-pCZZOT6meD8UCt5KWA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 19, 2020 at 12:04 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Thu, Nov 19, 2020 at 11:00:40AM +0100, Magnus Hagander wrote:
> > I'm thinking the code might get a lot cleaner if we just make a single
> > set of ifdefs, even if that means repeating the function header. In
> > theory we could put them in different *.c files as well, but that
> > seems overkill given how tiny they are.
>
> If you reorganize the code this way, I think that make coverage
> (genhtml mainly) would complain because the same function is defined
> multiple times. I have fallen in this trap recently, with 2771fcee.

Ugh, that's pretty terrible.

I guess the only way around that is then to split it up into separate
files. And while I think this way makes the code a lot easier to read,
and thereby safer, I'm not sure it's worth quite *that*.

Or do you know of some other way to get around that?

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2020-11-19 21:02:43 Re: VACUUM (DISABLE_PAGE_SKIPPING on)
Previous Message Andres Freund 2020-11-19 20:43:26 Re: Issue with server side statement-level rollback