On 28 October 2012 01:20, David Lee davidomu...@gmail.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
Since I've mentioned my use case, I might as well mention another issue I
stumbled across, which is that concurrent index creation cannot happen from
within trigger functions. I'm able to non-concurrently create indexes from
within trigger functions. Why is there this disparity?
Because
On Sun, Oct 28, 2012 at 8:22 AM, David Lee davidomu...@gmail.com wrote:
Thanks. Is this something viable as a feature request?
Just to contribute a tiny amount of data: I also get this request from
users on a semi-regular basis. It's definitely below the pains of
pg_dump/restore or
Thanks. Is this something viable as a feature request?
On Oct 28, 2012 7:48 AM, David Johnston pol...@yahoo.com wrote:
On Oct 27, 2012, at 19:20, David Lee davidomu...@gmail.com wrote:
Hey folks,
It seems like right now when you want to create an index concurrently,
the index creation
On Sat, Oct 27, 2012 at 7:20 PM, David Lee davidomu...@gmail.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
Thanks for all the responses.
I forgot to ask in my initial post: If not already available, is background
indexing a viable feature request? (This was why I sent to pgsql-hackers).
My use case is a multi-tenant CMS where indexes can be created by a web
front-end. Since web requests should
David Lee 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
On Sat, Oct 27, 2012 at 6:20 PM, David Lee davidomu...@gmail.com wrote:
Hey folks,
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
On Sun, Oct 28, 2012 at 8:20 AM, David Lee davidomu...@gmail.com wrote:
Hey folks,
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
On Sat, Oct 27, 2012 at 4:20 PM, David Lee davidomu...@gmail.com wrote:
Hey folks,
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
On Oct 27, 2012, at 19:20, David Lee davidomu...@gmail.com wrote:
Hey folks,
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
David Lee escribió:
Thanks for all the responses.
I forgot to ask in my initial post: If not already available, is background
indexing a viable feature request? (This was why I sent to pgsql-hackers).
My use case is a multi-tenant CMS where indexes can be created by a web
front-end.
Hey folks,
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
13 matches
Mail list logo
