OTECTED]>
To: "Marco Aurélio V. da Silva" <[EMAIL PROTECTED]>
Cc: "Tom Lane" <[EMAIL PROTECTED]>;
Sent: Wednesday, December 19, 2007 4:16 PM
Subject: Re: [GENERAL] Problem with collector statistic
On Dec 19, 2007 2:06 PM, Marco Aurélio V. da Silva
<[EMAI
On Dec 19, 2007 2:06 PM, Marco Aurélio V. da Silva
<[EMAIL PROTECTED]> wrote:
> Sorry,
>
> I discovered that the problem appears to be another, doing tests with the
> same database, this is a consultation limit using the same database and with
> 9364 records of the problem, and with 9363 not of.
ime=0.163..0.166 rows=1 loops=9363)"
" Index Cond: ("outer".codpagador = b.codcliente)"
"Total runtime: 1879.041 ms"
Thanks for your´s attention.
Marco Aurélio V. da Silva
Prodata Inf. e Cad. Ltda.
MSN: [EMAIL PROTECTED]
Fone: (33) 3322-3082
Marco Aurélio V. da Silva <[EMAIL PROTECTED]> writes:
> Select a.CodPagador,b.Descricao
> From Frete01 a Left Outer Join Frete02 b On (a.CodPagador = b.CodCliente)
>
> explain in good dabatase:
> "Limit (cost=0.00..46856.62 rows=55204 width=39) (actual
> time=11.205..536.761 rows=55204 loops=1)"
"=?iso-8859-1?Q?Marco_Aur=E9lio_V._da_Silva?=" <[EMAIL PROTECTED]> writes:
> Running a query on 2 database-equal, with the same indices, but with
> slightly different data, I have a very different result of performance. In
> one the index is used to make the join, in another it is seqscan.
The f
Dears,
Running a query on 2 database-equal, with the same indices, but with
slightly different data, I have a very different result of performance. In
one the index is used to make the join, in another it is seqscan.
The next consultation with explain.
Select a.CodPagador,b.Descricao
From Fr
