The first thing I made was vacuum/analyze them. Then I deleted and rebuilt the indicies but the problem remained. So I created a new table (e_catalogo2) with new indicies, I copied all data from the old table to the new one, weirdly the problem was solved. In my opinion there is something wrong (sometimes) in building indicies in Postgres, but of course, I am not sure. I wish to update to the last stable version but I fear the passing will be painful, when I updated from the 7.0 to 7.2 I had to modify some data structure because not compliant with the new version.
On 14/06/2004 20.58, Tom Lane <[EMAIL PROTECTED]> wrote: >NMB Webmaster <[EMAIL PROTECTED]> writes: >> I have two database quite similar, one has more tables than the >other. > >Are both of them vacuumed/analyzed recently? The slow plan seems >to be >estimating many more rows out of the e/m join than the other one. > >> My Postgres version is 7.2.3. Please help me , it is very important >to >> me to tune this query. > >I'd recommend an update, myself. 7.2.3 is old... > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that >your > message can get through to the mailing list cleanly > > > ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
