Re: [PERFORM] Problems with autovacuum

2009/5/25 Łukasz Jagiełło : > W dniu 25 maja 2009 17:32 użytkownik Scott Marlowe > napisał: >>> Recent change postgresql server from Amazon EC2 small into large one. >>> That gives me x86_64 arch, two core cpu and 7.5GB ram. Atm got almost >>> ~2000 small databases at that server and autovacuum wo

Re: [PERFORM] Problems with autovacuum

2009/5/25 Tom Lane : > With 2000 databases to cycle through, autovac is going to be spending > quite a lot of time just finding out whether it needs to do anything. > I believe the interpretation of autovacuum_naptime is that it should > examine each database that often, ie once a minute by default

Re: [PERFORM] Problems with autovacuum

=?UTF-8?B?xYF1a2FzeiBKYWdpZcWCxYJv?= writes: > That autovacuum working hole time, shoudn't be run only when db needs ? With 2000 databases to cycle through, autovac is going to be spending quite a lot of time just finding out whether it needs to do anything. I believe the interpretation of autova

Re: [PERFORM] Problems with autovacuum

W dniu 25 maja 2009 17:50 użytkownik Grzegorz Jaśkiewicz napisał: >> So, in 2000 databases, there's only an average of 2 relations per db >> and 102 dead rows?  Cause that's all you got room for with those >> settings. >> >> Whats the last 20 or so lines of vacuum verbose as run by a superuser say

Re: [PERFORM] Problems with autovacuum

W dniu 25 maja 2009 17:32 użytkownik Scott Marlowe napisał: >> Recent change postgresql server from Amazon EC2 small into large one. >> That gives me x86_64 arch, two core cpu and 7.5GB ram. Atm got almost >> ~2000 small databases at that server and autovacuum working hole time > >> postgresql.con

Re: [PERFORM] Problems with autovacuum

2009/5/25 Grzegorz Jaśkiewicz : > 2009/5/25 Scott Marlowe : > >> >> So, in 2000 databases, there's only an average of 2 relations per db >> and 102 dead rows?  Cause that's all you got room for with those >> settings. >> >> Whats the last 20 or so lines of vacuum verbose as run by a superuser say?

Re: [PERFORM] Problems with autovacuum

2009/5/25 Scott Marlowe : > > So, in 2000 databases, there's only an average of 2 relations per db > and 102 dead rows?  Cause that's all you got room for with those > settings. > > Whats the last 20 or so lines of vacuum verbose as run by a superuser say? according to http://www.postgresql.org/

Re: [PERFORM] Problems with autovacuum

2009/5/24 Łukasz Jagiełło : > Hi, > > Recent change postgresql server from Amazon EC2 small into large one. > That gives me x86_64 arch, two core cpu and 7.5GB ram. Atm got almost > ~2000 small databases at that server and autovacuum working hole time > postgresql.conf: > max_fsm_pages = 204800 >

Re: [PERFORM] Bad Plan for Questionnaire-Type Query

On Sun, May 24, 2009 at 2:42 PM, Tom Lane wrote: > > It still feels like this schema design is obscuring correlations that > the planner needs to know about in order to make decent estimates. I'm not sure how to make the planner aware of these correlations. Is there something inherently flawed w

[PERFORM] Putting tables or indexes in SSD or RAM: avoiding double caching?

Hi, I have sen many posts on using SSDs, and iodrive in particular, to accelerate the performance of Postgresql (or other DBMS) -- e.g. this discussion. I have also seen the su