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

From Robert Haas
Subject Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS
Date
Msg-id CA+TgmoZ5YfmGzO_HrYmh5oG1MioyKb57dd_vV=G4Nx8vsuf4=w@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 6:17 AM, 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.

Oops.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument
Next
From: Robert Haas
Date:
Subject: Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index