Postgres Pro
Downloads
Home   >   mailing lists

pg_prewarm really needs some CHECK_FOR_INTERRUPTS - Mailing list pgsql-hackers

From Andres Freund
Subject pg_prewarm really needs some CHECK_FOR_INTERRUPTS
Date
Msg-id 20141111111711.GF22216@alap3.anarazel.de
Whole thread Raw
Responses Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS  (Michael Paquier <michael.paquier@gmail.com>)
Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS  (Robert Haas <robertmhaas@gmail.com>)
Re: pg_prewarm really needs some CHECK_FOR_INTERRUPTS  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Tree view 
Hi,

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.

Greetings,

Andres Freund

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

pgsql-hackers by date:

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