On Wed, 7 Jul 2010, JOUANIN Nicolas (44) wrote:
It seems to work fine (same execution plan and less duration) after :
- setting default_statistics_target to 100
- full vacuum with analyze
Don't do VACUUM FULL.
Matthew
--
I suppose some of you have done a Continuous Maths course. Yes? Contin
It seems to work fine (same
execution plan and less duration) after :
- setting default_statistics_target to 100
- full vacuum with analyze
- reindexdb
Thanks.
Message original
Sujet : Re: [PERFORM] Two different execution plan for the same request
De : Guillaume Smet
Hi Nicolas,
On Wed, Jul 7, 2010 at 10:47 AM, JOUANIN Nicolas (44)
wrote:
> There were no modification made on the database except a restart yesterday
> evening and a vacuumdb --analyse ran at night.
It's not really surprising considering you probably kept the
default_statistics_target to 10 (it
JOUANIN Nicolas (44) wrote:
The strange thing is that this morning explain analyze now gives a
much better duration :
There were no modification made on the database except a restart
yesterday evening and a vacuumdb --analyse ran at night.
If the earlier bad query was run on a fresh imported
Nicolas Jouanin
Analyste - TVA8ième directive
Bureau SI-1C / DAP2
Tel: 02.51.88.50.18
Adoptez l'éco-attitude.
N'imprimez ce courriel que si c'est
vraimen
JOUANIN Nicolas (44) wrote:
Hi,
I've trouble with some SQL request which have different execution
plans when ran on two different servers. One server is the development
environment, the othe rone is th pre-production env.
Both servers run postgreSQL 8.3.0 on Linux and :
- both databases cont
