rows)
-Mensaje original-
De: Christopher Browne [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 01 de agosto de 2003 18:27
Para: Fernando Papa
CC: [EMAIL PROTECTED]
Asunto: Re: [PERFORM] I can't wait too much: Total runtime 432478.44 msec
I'd point at the following as being a sterling
)
-Mensaje original-
De: Josh Berkus [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 01 de agosto de 2003 18:32
Para: Christopher Browne; Fernando Papa
CC: [EMAIL PROTECTED]
Asunto: Re: [PERFORM] I can't wait too much: Total runtime 432478.44
msec
Fernando,
AND cont_publicacion.fecha_publicacion
= 2::numeric) AND (id_sbc =
619::numeric) AND (id_tipo = 2::numeric))
Total runtime: 486445.19 msec
(20 rows)
-Mensaje original-
De: Mendola Gaetano [mailto:[EMAIL PROTECTED]
Enviado el: sábado, 02 de agosto de 2003 7:36
Para: [EMAIL PROTECTED]
CC: Fernando Papa
Asunto: Re: I can't wait
Title: Mensaje
Hi
Volker!!! I think you're right. Look at times:
QUERY
PLAN
---Limit
(cost=23.37..23.37 rows=1 width=487)
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't wait too
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
-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't an
