| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | David Lee <davidomundo(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Creating indexes in the background |
| Date: | 2012-10-29 13:29:50 |
| Message-ID: | CA+U5nMKCrEaNn7_dxRAwUJm=5fNQ62KLRjPaA8ZK-oc5Z1yROQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 October 2012 01:20, David Lee <davidomundo(at)gmail(dot)com> wrote:
> It seems like right now when you want to create an index concurrently, the index creation will get canceled if you cancel the statement (i.e. you must keep your statement open).
>
> Is there a way to "launch" an index creation in the background so that the statement doesn't need to be kept open?
There is some work in 9.3 that will give low-level infrastructure
support to allow the concept of a "job/task scheduler" in Postgres,
which is the generic description of the facility you're looking for.
It is early days, but that will emerge sometime in 9.3 or beyond.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-10-29 13:31:04 | Proposal for Allow postgresql.conf values to be changed via SQL |
| Previous Message | Kevin Grittner | 2012-10-29 12:48:49 | Re: Index creation in postgresql |