fardeen memon <[EMAIL PROTECTED]> writes:
> here is the output of the explain query after changing the tra_date
> column to timestamp.
If you want intelligent commentary, please (a) post EXPLAIN ANALYZE not
EXPLAIN output, and (b) don't mangle the indentation. This is just
about unreadable :
Thanks for the reply .. you are right after i changed tra_date to timestamp in the view it considered the index and the performance did increase a bit .. but still compared to the query without the joins its much less .. any idea why? here is the output of the explain query after changi
fardeen memon <[EMAIL PROTECTED]> writes:
> What is it that i am doing wrong?
I think the forced coercion to date type in the view case is preventing
the planner from making a good guess about the selectivity of the
condition on tra_date. It has stats about tra_date's distribution,
but none about
Hi
i have a severe performance problem with one of my
views which has 6 to 8 joins .. any help will be
appreciated..
the view is:
CREATE OR REPLACE VIEW thsn.trade_view AS
SELECT tra.tra_id, tra.per_id, tra.fir_id,
tra.tra_dcn, tra.tra_startdate::date AS tra_startdate,
tra.tra_enddate::date AS
