Skip site navigation (1) Skip section navigation (2)

Re: Hash join on int takes 8..114 seconds

From: "Andrus" <kobruleht2(at)hot(dot)ee>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Richard Huxton" <dev(at)archonet(dot)com>,"PFC" <lists(at)peufeu(dot)com>,<pgsql-performance(at)postgresql(dot)org>
Subject: Re: Hash join on int takes 8..114 seconds
Date: 2008-11-21 19:45:11
Message-ID: A44943E272DF48CC9BC306C513387020@andrusnotebook (view raw or flat)
Thread:
Lists: pgsql-performance
Alvaro,

> Are you really using vacuum_cost_delay=2000?  If so, therein lies your
> problem.  That's a silly value to use for that variable.  Useful values
> are in the 20-40 range probably, or maybe 10-100 being extremely
> generous.

Thank you.
My 8.1.4 postgresql.conf does not contain such option. So vacuum_cost_delay 
is off probably.
Since doc does not recommend any value, I planned to use 2000

Will value of 30 allow other clients to work when VACUUM FULL is running ?

Uncommented relevant values in postgresql.conf file are:

shared_buffers = 15000
work_mem = 512
maintenance_work_mem = 131072
fsync = on
effective_cache_size= 70000
log_min_duration_statement= 30000

Andrus. 


In response to

Responses

pgsql-performance by date

Next:From: Alvaro HerreraDate: 2008-11-21 19:48:05
Subject: Re: Hash join on int takes 8..114 seconds
Previous:From: Alvaro HerreraDate: 2008-11-21 19:16:46
Subject: Re: Hash join on int takes 8..114 seconds

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group