On Thu, Mar 5, 2009 at 1:30 PM, Tom Lane wrote:
> Jonathan Hseu writes:
>> Sort (cost=11684028.44..11761274.94 rows=30898601 width=40)
>> Sort Key: "time"
>> -> Bitmap Heap Scan on ticks (cost=715657.57..6995196.08 rows=30898601
>> width=40)
>> Recheck Cond: (contract_id = 1)
>
Oops, forgot to CC my reply to the list. Sorry if this gets messed up.
On Thu, Mar 5, 2009 at 12:30 PM, Tom Lane wrote:
> Jonathan Hseu writes:
> > Sort (cost=11684028.44..11761274.94 rows=30898601 width=40)
> >Sort Key: "time"
> >-> Bitmap Heap Scan on ticks (cost=715657.57..69951
On Thu, Mar 5, 2009 at 12:58 PM, Joshua D. Drake wrote:
> What happens if you do this:
>
> SET cpu_tuple_cost TO '0.5';
> SET cpu_index_tuple_cost TO '0.5';
> EXPLAIN ANALYZE 8.3 query
>
Right now, I'm getting very good results with the above. I'm still running
additional tests but I'll keep
On Thu, Mar 5, 2009 at 1:57 PM, Kevin Grittner
wrote:
Aaron Guyon wrote:
>> 8.3.3: 1195 ms
>> 8.2.12: 611 ms
>
> Could you send the non-commented lines from the postgresql.conf files
> from both installations?
>
> If feasible, update to the latest bug-fix version of 8.3.
>
> Also, if you hav
>>> Aaron Guyon wrote:
> 8.3.3: 1195 ms
> 8.2.12: 611 ms
Could you send the non-commented lines from the postgresql.conf files
from both installations?
If feasible, update to the latest bug-fix version of 8.3.
Also, if you haven't already done so, try setting effective_cache_size
= '3GB' an
Jonathan Hseu writes:
> Sort (cost=11684028.44..11761274.94 rows=30898601 width=40)
>Sort Key: "time"
>-> Bitmap Heap Scan on ticks (cost=715657.57..6995196.08 rows=30898601
> width=40)
> Recheck Cond: (contract_id = 1)
> -> Bitmap Index Scan on contract_id_time_idx
Matching query plans with numerics changed to integers.
I sent the wrong query plans earlier
8.3.3: 1195 ms
8.2.12: 611 ms
I have a relatively simple query with a single index on (contract_id, time):
vjtrade=> EXPLAIN SELECT * FROM ticks WHERE contract_id=1 ORDER BY time;
QUERY
PLAN
On Thu, Mar 5, 2009 at 10:20 AM, Kevin Grittner
wrote:
Robert Haas wrote:
>> Well, it looks like the problem is that 8.3 is not using the index
>> idx_bundle_content_bundle_id. But I don't know why that should be
>> happening, unless there's a problem with that index.
>
> I didn't see that
On Wed, Mar 4, 2009 at 6:20 PM, Aaron Guyon wrote:
> On Tue, Mar 3, 2009 at 5:34 PM, Tom Lane wrote:
>>
>> Comparisons on
>> numerics aren't terribly fast though (in either release). I wonder
>> whether you could change the key columns to int or bigint.
>
> I changed the affected columns from nu
10 matches
Mail list logo
