Re: consulta se demora mucho mas que antes

> Invertir el orden no ayudo mucho:
>
> radius=# explain
> radius-# select 'quemados',sum(acctsessiontime)/60 as minutos,
> sum(roundedsessiontime)/60 as redondeados
> radius-# from stopacct a inner join pines b on (a.username = b.pin)
> radius-# where h323disconnecttime::date = '2006-03-29'::date
> radius-# and h323callorigin = 'originate'
> radius-# and idproducto in (11,40,41);
> QUERY PLAN
> ----------------------------------------------------------------------------------------------------------------------------
> Aggregate (cost=393646.90..393646.91 rows=1 width=16)
> -> Nested Loop (cost=0.00..393639.84 rows=1411 width=16)
> -> Seq Scan on stopacct a (cost=0.00..382461.38 rows=1853
> width=31)
> Filter: (((h323disconnecttime)::date =
> '2006-03-29'::date) AND ((h323callorigin)::text = 'originate'::text))
> -> Index Scan using pines_pkey on pines b (cost=0.00..6.02
> rows=1 width=13)
> Index Cond: (("outer".username)::text = (b.pin)::text)
> Filter: ((idproducto = 11) OR (idproducto = 40) OR
> (idproducto = 41))
> (7 rows)

Me da la impresion de que el cast ese a date no ayuda mucho. Que pasa
si usas algo como

WHERE h323disconnecttime between
'2006-03-29'::timestamptz and '2006-03-30'::timestamptz
and h323callorigin = 'originate'

(obviamente cambia timestamptz a timestamp si tu campo no tiene TZ, lo
cual seria un error)

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support