Re: PG 10: could not generate random cancel key - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PG 10: could not generate random cancel key
Date
Msg-id CA+TgmoY4R6nfKxnU6DU34Qe5A=ALOQJDXDVu4jiqJ7PCkyiheQ@mail.gmail.com
Whole thread Raw
In response to Re: PG 10: could not generate random cancel key  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: PG 10: could not generate random cancel key  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Jul 17, 2018 at 1:27 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> On 2018-Jul-17, Robert Haas wrote:
>
>> On Tue, Jul 17, 2018 at 8:33 AM, Dean Rasheed <dean.a.rasheed@gmail.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?

Ugh, I'm not doing very well today, am I?  I read that as while() but
it says if().

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Vacuum: allow usage of more than 1GB of work mem
Next
From: Alvaro Herrera
Date:
Subject: Re: Internal error XX000 with enable_partition_pruning=on, pg 11beta1 on Debian