We routinely use plantuner. http://www.sai.msu.su/~megera/wiki/plantuner
On Tue, May 20, 2014 at 12:38 PM, Steve Crawford
scrawf...@pinpointresearch.com wrote:
Is there a way to force a specific index to be removed from consideration in
planning a single query?
Specifically, on a
Is there a way to force a specific index to be removed from
consideration in planning a single query?
Specifically, on a 60-million-row table I have an index that is a
candidate for removal. I have identified the sets of nightly queries
that use the index but before dropping it I would like
On 5/20/14, 1:38 PM, Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
hi Steve,
What is the query? Or at least a sanitized but complete version?
Thanks,
Seamus
PS. I've had luck hinting with OFFSET 0 but it might not
Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
Specifically, on a 60-million-row table I have an index that is a
candidate for removal. I have identified the sets of nightly queries
that use the index but before
On 05/20/2014 09:44 AM, Seamus Abshere wrote:
On 5/20/14, 1:38 PM, Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
hi Steve,
What is the query? Or at least a sanitized but complete version?
I've now resolved the
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
Specifically, on a 60-million-row table I have an index that is a
candidate for removal. I have identified the sets of
On 05/20/2014 11:48 AM, Steve Crawford wrote:
...
What would happen if you did:
BEGIN;
DROP INDEX bothersome_idx;
INSERT INTO indexed_table...;
ROLLBACK;
Never mind. Thought it through.
Cheers,
Steve
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to
Steve Crawford scrawf...@pinpointresearch.com writes:
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
If you can afford to lock the table for a while, the easiest is
BEGIN;
DROP INDEX bothersome_idx;
EXPLAIN your_query;
ROLLBACK;
Interesting. But what do you mean by a while? Does the above
Steve Crawford wrote
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
Specifically, on a 60-million-row table I have an index that is a
candidate for removal. I have
Steve Crawford wrote:
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
If you can afford to lock the table for a while, the easiest is
BEGIN;
DROP INDEX bothersome_idx;
EXPLAIN your_query;
ROLLBACK;
Interesting. But what do you mean by a while? Does the above keep
the index intact (brief
On Tue, May 20, 2014 at 11:48 AM, Steve Crawford
scrawf...@pinpointresearch.com wrote:
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
Steve Crawford wrote:
Is there a way to force a specific index to be removed from
consideration in planning a single query?
Specifically, on a
On Tue, May 20, 2014 at 3:20 PM, Jeff Janes [via PostgreSQL]
ml-node+s1045698n580459...@n5.nabble.com wrote:
On Tue, May 20, 2014 at 11:48 AM, Steve Crawford [hidden
email]http://user/SendEmail.jtp?type=nodenode=5804596i=0
wrote:
On 05/20/2014 10:44 AM, Alvaro Herrera wrote:
Steve
Jeff Janes wrote:
Best case, 'A while' means however long it takes the explain (possibly
analyze) to run, and for you to then type 'rollback;'
worse case, someone else is already holding an incompatible lock (i.e. any
lock) on the table, and is going to hang on to it for a long while, so
13 matches
Mail list logo
