Yes, casting the result improved the time response a lot. Thank you!
Reimer > -----Mensagem original----- > De: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] nome de Tom Lane > 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" <[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, maybe you need to cast the result of > the concatenation to char(8) to get it to use the index. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > > ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
