| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | pg_prewarm really needs some CHECK_FOR_INTERRUPTS |
| Date: | 2014-11-11 11:17:11 |
| Message-ID: | 20141111111711.GF22216@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg스포츠 토토 결과SQL |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2014-11-11 11:26:00 | Re: What exactly is our CRC algorithm? |
| Previous Message | Etsuro Fujita | 2014-11-11 10:01:04 | Re: PENDING_LIST_CLEANUP_SIZE - maximum size of GIN pending list Re: HEAD seems to generate larger WAL regarding GIN index |