Re: [PERFORM] FSM - per database or per installation?

2009-12-23 Thread Alvaro Herrera
Craig James wrote: > Heikki Linnakangas wrote: > >The parameter is gone in 8.4, BTW. > > Both max_fsm_relations and max_fsm_pages? Yes, both are gone. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 sup

Re: [PERFORM] FSM - per database or per installation?

2009-12-23 Thread Scott Marlowe
On Wed, Dec 23, 2009 at 6:38 PM, Craig James wrote: > Heikki Linnakangas wrote: >> >> Craig James wrote: >>> >>> Are the FSM parameters for each database, or the entire Postgres >>> system?  In other words, if I have 100 databases, do I need to increase >>> max_fsm_pages and max_fsm_relations by a

Re: [PERFORM] FSM - per database or per installation?

2009-12-23 Thread Craig James
Heikki Linnakangas wrote: Craig James wrote: Are the FSM parameters for each database, or the entire Postgres system? In other words, if I have 100 databases, do I need to increase max_fsm_pages and max_fsm_relations by a factor of 100, or keep them the same as if I just have one database? I s

Re: [PERFORM] hardware priority for an SSD database?

2009-12-23 Thread Greg Smith
Ben Chobot wrote: With most data stored in flash, does it still make sense to buy as much ram as possible? RAM is still faster than flash, but while it's cheap, it isn't free, and our database is a couple hundred GB in size. Depends on the actual working set of data you run into on a regular

[PERFORM] hardware priority for an SSD database?

2009-12-23 Thread Ben Chobot
We're looking to upgrade our database hardware so that it can sustain us while we re-architect some of the more fundamental issues with our applications. The first thing to spend money on is usually disks, but our database currently lives almost entirely on flash storage, so that's already