Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
o -> Seq Scan on cont_contenido (cost=0.00..9.70 rows=3 width=112) (actual time=0.65..28.98 rows=8 loops=1) Filter: ((id_instalacion = 2::numeric) AND (id_sbc = 619::numeric) AND (id_tipo = 2::numeric)) Total runtime: 720595.77 msec (20 rows) ---

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
I was play with nested loops, and I found this: Original explain: Limit (cost=9.75..9.76 rows=1 width=479) (actual time=436858.90..436858.93 rows=8 loops=1) -> Sort (cost=9.75..9.76 rows=1 width=479) (actual time=436858.88..436858.89 rows=8 loops=1) Sort Key: cont_publicacion.fe

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
Err... you're right... one of us say the same thing when I show the Volker mail... -Mensaje original- De: Manfred Koizar [mailto:[EMAIL PROTECTED] Enviado el: lunes, 04 de agosto de 2003 12:17 Para: Fernando Papa CC: Volker Helm; [EMAIL PROTECTED] Asunto: Re: [PERFORM] I can'

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
Title: Mensaje Hi Volker!!! I think you're right. Look at times:    QUERY PLAN -

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
-> Seq Scan on cont_contenido (cost=0.00..9.70 rows=3 width=112) (actual time=0.47..7.48 rows=8 loops=1) Filter: ((id_instalacion = 2::numeric) AND (id_sbc = 619::numeric) AND (id_tipo = 2::numeric)) Total runtime: 486445.19 msec (20 rows) -Mensaje original- De: Mendola

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
Filter: ((id_instalacion = 2::numeric) AND (id_sbc = 619::numeric) AND (id_tipo = 2::numeric)) Total runtime: 449765.69 msec (20 rows) -Mensaje original- De: Josh Berkus [mailto:[EMAIL PROTECTED] Enviado el: viernes, 01 de agosto de 2003 18:32 Para: Christopher Browne; Fe

Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-04 Thread Fernando Papa
=1) Filter: ((id_instalacion = 2::numeric) AND (id_sbc = 619::numeric) AND (id_tipo = 2::numeric)) Total runtime: 465088.66 msec (21 rows) -Mensaje original- De: Christopher Browne [mailto:[EMAIL PROTECTED] Enviado el: viernes, 01 de agosto de 2003 18:27 Pa

[PERFORM] I can't wait too much: Total runtime 432478.44 msec

2003-08-01 Thread Fernando Papa
Title: Mensaje   Hi all! Really I don't know what happened with this query. I'm running PG 7.3.1 on solaris, vaccumed (full) every nigth. The cardinality of each table was:   cont_contenido: 97 rows juegos_config: 40 rows cont_publicacion: 446 rows not huge tables...   however, this query

Re: [PERFORM] Similar querys, better execution time on worst execution plan

2003-06-26 Thread Fernando Papa
> -Mensaje original- > De: SZUCS Gábor [mailto:[EMAIL PROTECTED] > Enviado el: jueves, 26 de junio de 2003 7:31 > Para: [EMAIL PROTECTED] > Asunto: Re: [PERFORM] Similar querys, better execution time > on worst execution plan > > > Fernando, > > 1. Try EXPLAIN ANALYZE. Cost alone isn'

[PERFORM] Similar querys, better execution time on worst execution plan

2003-06-25 Thread Fernando Papa
Hi all! I have a strange behavior with this query: SELECT c.id_contenido,p.fecha_publicacion,c.titulo_esp,c.activo,c.activo,s.label_esp as label_sbc,p.orden ,p.tapa_spc,p.tapa_cat,p.tapa_principal,p.id_publicacion,ca.label_esp as label_cat,sp.label_esp as label_spc FROM cont_contenido c ,cont_p