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

From Andres Freund
Subject Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS
Date
Msg-id 20141112202935.GF13473@awork2.anarazel.de
Whole thread Raw
In response to pg_prewarm really needs some CHECK_FOR_INTERRUPTS  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 2014-11-11 12:17:11 +0100, Andres Freund 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.

Pushed to master and 9.4.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: nill
Date:
Subject: Reverse Engineering - search constraints are not explicitly stated in the tables from the VIEW
Next
From: Kirk Roybal
Date:
Subject: Error building the EnterpriseDB mysql_fdw on OSX