Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran
Date
Msg-id CA+TgmoZve5mg3EVUuWX9K4yQXKLtMkR214Ov_hhbXvPYvRVj3A@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Oct 17, 2016 at 10:50 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The real issue here is whether we are willing to say that
> Postgres simply does not work anymore on machines without standard entropy
> sources.  Doesn't matter whether the user cares about the strength of
> cancel keys, we're just blowing them off.  That seems a bit extreme
> from here.  I think we should be willing to fall back to the old code
> if we can't find a real entropy source.

+1.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Better logging of COPY queries if log_statement='all'
Next
From: Heikki Linnakangas
Date:
Subject: Re: [COMMITTERS] pgsql: Replace PostmasterRandom() with a stronger way of generating ran