pgsql-performance@postgresql.org
> Assunto: Re: [PERFORM] Improving SQL performance
>
>
> "Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> > I know that the problem with the following SQL is the "LOG.CODCEP =
> > ENDE.CODCEP||CODLOG" condition, but what ca
"i_fk_log_bai" btree (codbai)
"i_lc_log_codcep" btree (codcep)
Any clue?
Thanks!
Reimer
-Mensagem original-
De: Tom Lane [mailto:[EMAIL PROTECTED]
Enviada em: quinta-feira, 11 de janeiro de 2007 16:31
Para: [EMAIL PROTECTED]
Cc: pgsql-performance@postgr
ensagem original-
> De: Tom Lane [mailto:[EMAIL PROTECTED]
> Enviada em: quinta-feira, 11 de janeiro de 2007 16:31
> Para: [EMAIL PROTECTED]
> Cc: pgsql-performance@postgresql.org
> Assunto: Re: [PERFORM] Improving SQL performance
>
>
> "Carlos H. Reimer" <[EM
"Carlos H. Reimer" <[EMAIL PROTECTED]> writes:
> I know that the problem with the following SQL is the "LOG.CODCEP =
> ENDE.CODCEP||CODLOG" condition, but what can I
> do to improve the performance?
Seems the problem is not using an index for tt_log. Do you have an
index on tt_log.codcep? If so,
Carlos H. Reimer wrote:
Hi,
I know that the problem with the following SQL is the "LOG.CODCEP =
ENDE.CODCEP||CODLOG" condition, but what can I
do to improve the performance?
I wouldn't say it's the join condition. There is a nested loop join on
500k+ rows.
Is it possible to put an index
Hi,
I know that the problem with the following SQL is the "LOG.CODCEP =
ENDE.CODCEP||CODLOG" condition, but what can I
do to improve the performance?
Is there a type of index that could help or is there another way to build
this SQL?
Thank you in advance!
explain analyze
SELECT ENDE.* , DEND.DE
