Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Robert Haas
>> > That is interesting. It would also be interesting to total up the time it >> > takes to run EXPLAIN (without ANALYZE) for a large number of queries. > I wonder if we'd see anything dramatically different using PREPARE... Well... the point here is to measure planning time. I would think that

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Robert Treat
On Friday 05 December 2008 00:05:34 Robert Haas wrote: > On Thu, Nov 27, 2008 at 6:46 PM, Gregory Stark <[EMAIL PROTECTED]> wrote: > >> ANALYZE with default_statistics_target set to 10 takes 13 s. With > >> 100, 92 s. With 1000, 289 s. > > > > That is interesting. It would also be interesting to

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Robert Haas
On Fri, Dec 5, 2008 at 2:16 PM, Guillaume Smet <[EMAIL PROTECTED]> wrote: > On Fri, Dec 5, 2008 at 8:11 PM, Robert Haas <[EMAIL PROTECTED]> wrote: >> Correct. As compared with 8.2.9, ANALYZE was substantially faster, >> but query planning was significantly slower. >> >> Thanks also to Greg for rep

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Robert Haas
>> Thanks also to Greg for reposting my emails. I didn't even realize I >> hadn't sent them to the list. > > Any chance you could do the same test with a 8.3? It could be > interesting to see if it's a HEAD thing or if the slow down was > introduced in 8.3. Somehow I knew you were going to ask th

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Guillaume Smet
On Fri, Dec 5, 2008 at 8:11 PM, Robert Haas <[EMAIL PROTECTED]> wrote: > Correct. As compared with 8.2.9, ANALYZE was substantially faster, > but query planning was significantly slower. > > Thanks also to Greg for reposting my emails. I didn't even realize I > hadn't sent them to the list. Any

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Robert Haas
> On Fri, Dec 5, 2008 at 7:24 PM, Greg Smith <[EMAIL PROTECTED]> wrote: >> comparing to 8.2.9 results: >> - q1 was 32% slower with dst = 10, 33% slower with dst = 1000 >> - other queries were 19% slower with dst = 10, 25% slower with dst = 1000 > > You mean that HEAD is slower than 8.2.9 or I don't

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Guillaume Smet
Robert, On Fri, Dec 5, 2008 at 7:24 PM, Greg Smith <[EMAIL PROTECTED]> wrote: > comparing to 8.2.9 results: > - q1 was 32% slower with dst = 10, 33% slower with dst = 1000 > - other queries were 19% slower with dst = 10, 25% slower with dst = 1000 You mean that HEAD is slower than 8.2.9 or I don'

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-05 Thread Greg Smith
Looks like Robert accidentally answered my question about what version his results were from off-list. Here's his update: --- Unfortunately it was 8.2.9, as I realized halfway into the run. Here are the results from a CVS HEAD checkout last night. *** Query planning times q1 (the complex

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-04 Thread Greg Smith
On Fri, 5 Dec 2008, Robert Haas wrote: OK, I did this. I actually tried 10 .. 100 in increments of 10 and then 100 ... 1000 in increments of 50, for 7 different queries of varying complexity Great bit of research. Was this against CVS HEAD or an 8.3 database? -- * Greg Smith [EMAIL PROTECTE

Re: [HACKERS] default statistics target testing (was: Simple postgresql.conf wizard)

2008-12-04 Thread Robert Haas
On Thu, Nov 27, 2008 at 6:46 PM, Gregory Stark <[EMAIL PROTECTED]> wrote: >> ANALYZE with default_statistics_target set to 10 takes 13 s. With >> 100, 92 s. With 1000, 289 s. > > That is interesting. It would also be interesting to total up the time it > takes to run EXPLAIN (without ANALYZE) for