From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Maxwell <gmaxwell(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How does the planner deal with multiple possible |
Date: | 2006-07-21 13:52:44 |
Message-ID: | 1153489964.2846.6.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ühel kenal päeval, R, 2006-07-21 kell 08:29, kirjutas Jim C. Nasby:
> No, this is 8.1.3, and it's a production machine so I'd prefer not to go
> about dropping indexes to get cost comparisons; unless there's some way
> to disable the use of an index in a given backend?
Currently the closest thing is
BEGIN;
DROP INDEX xxx;
test query here
ABORT;
> Otherwise I'll try
> and come up with a test case.
--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-07-21 13:55:31 | Re: How does the planner deal with multiple possible indexes? |
Previous Message | Albe Laurenz | 2006-07-21 13:48:31 | Re: Transaction Speed and real time database |