Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS
Date
Msg-id CAB7nPqTdzggRbJv_cXOOXN_61t3ZKj_DOVRUw7+q83ak3JjNmA@mail.gmail.com
Whole thread Raw
In response to pg_prewarm really needs some CHECK_FOR_INTERRUPTS  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Tue, Nov 11, 2014 at 8:17 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> pg_prewarm() currently can't be cannot be interrupted - which seems odd
> given that it's intended to read large amounts of data from disk. A
> rather slow process.
>
> Unless somebody protests I'm going to add a check to the top of each of
> the three loops.
Good idea, +1.
-- 
Michael



pgsql-hackers by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: Re: What exactly is our CRC algorithm?
Next
From: Fujii Masao
Date:
Subject: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index