Re: PG 10: could not generate random cancel key

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 10: could not generate random cancel key
Date: 2018-07-17 17:27:48
Message-ID: 20180717172748.mh5snsc2gn42qfed@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-Jul-17, Robert Haas wrote:

> On Tue, Jul 17, 2018 at 8:33 AM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> > if (RAND_status() == 0)
> > RAND_poll();
>
> Looks like a recipe for an infinite loop. At least, I think we ought
> to have a CHECK_FOR_INTERRUPTS() in that loop.

What loop?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-07-17 17:30:15 Re: Vacuum: allow usage of more than 1GB of work mem
Previous Message Heikki Linnakangas 2018-07-17 17:21:20 Re: chained transactions