"Radhika Sambamurti" <[EMAIL PROTECTED]> writes:
> When I run the query with combination of FirmClearingID & status the run
> times are approx 3700ms.
> But when I add tradedate ie date_trunc('day', tradedate) = '20070703' the
> run time becomes a horrendous 19631.958 ms.
I'm not really able to m
Hi,
I have a complicated view joining 3 tables.
Here are the run times:
LOG: duration: 3380.672 ms statement: explain analyze SELECT * from
vtradeblock where FirmClearingid = 'FIRMA' and status = 1;
LOG: duration: 3784.152 ms statement: explain analyze SELECT * from
vtradeblock where date_tr
Theo Galanakis wrote:
Have a question regarding when a Query Plan uses an Index.
I have a basic statement
This query uses the Index Scan:
explain analyse select * from tablea where columna_id < 57
This query uses Seq Scan:
explain analyse select * from tablea where columna_id < 58
There are about 5
Title: Query Plan
Have a question regarding when a Query Plan uses an Index.
I have a basic statement
This query uses the Index Scan:
explain analyse select * from tablea where columna_id < 57
This query uses Seq Scan:
explain analyse select * from tablea where columna_id < 58
There a
Have you run ANALYZE recently?
Please send back EXPLAIN ANALYZE for the below query.
> EXPLAIN from DB 2 (doesn't come back):
>QUERY PLAN
>
Hi, I have two databases that were created with identical schemas and
both filled in the exact same way, with the same indices etc., yet
they give different query paths for identical SELECTs. Normally this
wouldn't bug me, but one DB returns the select in relatively short
order, while the other one
