> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
>
> [ fools around with it for awhile... ] I think this is already fixed
> for 8.2.1. Note the costs of the two related index scans:
I installed 8.2.1 this morning and it works much better.
"Dave Dutcher" <[EMAIL PROTECTED]> writes:
> Here is the table definition. Thanks.
[ fools around with it for awhile... ] I think this is already fixed
for 8.2.1. Note the costs of the two related index scans:
8.2.0:
-> Bitmap Index Scan on om_transaction_om_transaction_index
(cost
compairison is still valid.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adam Rich
Sent: Thursday, January 04, 2007 7:19 PM
To: 'Dave Dutcher'; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Slow Query on Postgres 8.2
Dave,
Is it me
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
>
> Um ... what indexes has this table got exactly? It's very
> unclear what
> alternatives the planner is being faced with.
>
Here is the table definition. Thanks.
:32 PM
To: pgsql-performance@postgresql.org
Subject: [PERFORM] Slow Query on Postgres 8.2
Hello,
I am looking at upgrading from 8.1.2 to 8.2.0, and I've found a query
which runs a lot slower. Here is the query:
select type, currency_id, instrument_id, sum(amount) as total_amount
"Dave Dutcher" <[EMAIL PROTECTED]> writes:
> I am looking at upgrading from 8.1.2 to 8.2.0, and I've found a query which
> runs a lot slower.
Um ... what indexes has this table got exactly? It's very unclear what
alternatives the planner is being faced with.
regards, tom
Hello,
I am looking at upgrading from 8.1.2 to 8.2.0, and I've found a query which
runs a lot slower. Here is the query:
select type, currency_id, instrument_id, sum(amount) as total_amount from
om_transaction
where
strategy_id in
('BASKET1','BASKET2','BASKET3','BASKET4','BASKET5','BASKET6',
