Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)
Date: 1999-05-17 14:49:51
Message-ID: 9313.926952591@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> I found the problem. I modified my test script to add 'vacuum analyze'
> after creating test data and it works really fast ! Great !
> Now I'm wondering why do I need vacuum analyze after creating test data
> and indices ?

VACUUM ANALYZE would create pg_statistics entries for the tables,
which'd allow the optimizer to make better estimates of restriction
and join selectivities. I expect that it changes the plan being used;
what does EXPLAIN say with and without the analyze?

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-05-17 15:24:31 Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)
Previous Message Oleg Bartunov 1999-05-17 14:25:07 Re: [HACKERS] GEQO optimizer (was Re: Backend message type 0x44 arrived while idle)