Re: [PERFORM] PostgreSQL Configuration Tool for Dummies

2007-06-26 Thread Greg Smith
On Tue, 26 Jun 2007, Josh Berkus wrote: I find it extremely inconsistent that you want to select "middle-of-the-road" defaults for some values and ask users detailed questions for other values. Which are we trying to do, here? I'd like to see people have a really simple set of questions to get

Re: [PERFORM] PostgreSQL Configuration Tool for Dummies

2007-06-26 Thread Josh Berkus
Greg, > Your max_connections concern is one fact that haunts the idea of just > giving out some sample configs for people. Lance's tool asks outright the > expectation for max_connections which I think is the right thing to do. ... > I think people are stuck with actually learning a bit about wor

Re: [PERFORM] Database-wide VACUUM ANALYZE

2007-06-26 Thread Alvaro Herrera
Steven Flatt escribió: > Most of our large (partitioned) tables are insert-only (truncated > eventually) so will not be touched by autovacuum until wraparound prevention > kicks in. However the tables are partitioned by timestamp so tables will > cross the 1.9 billion marker at different times (s

Re: [PERFORM] PostgreSQL Configuration Tool for Dummies

2007-06-26 Thread Greg Smith
On Tue, 26 Jun 2007, Josh Berkus wrote: The problem is that there are no "safe, middle-of-the-road" values for some things, particularly max_connections and work_mem. Your max_connections concern is one fact that haunts the idea of just giving out some sample configs for people. Lance's tool

Re: [PERFORM] Database-wide VACUUM ANALYZE

2007-06-26 Thread Steven Flatt
On 6/25/07, Jim Nasby <[EMAIL PROTECTED]> wrote: If you set that to 2B, that means you're 2^31-"2 billion"-100 transactions away from a shutdown when autovac finally gets around to trying to run a wraparound vacuum on a table. If you have any number of large tables, that could be a big probl

Re: [PERFORM] PostgreSQL Configuration Tool for Dummies

2007-06-26 Thread Josh Berkus
Greg, > We've hashed through this area before, but for Lance's benefit I'll > reiterate my dissenting position on this subject. If you're building a > "tool for dummies", my opinion is that you shouldn't ask any of this > information. I think there's an enormous benefit to providing something >

Re: [PERFORM] Volunteer to build a configuration tool

2007-06-26 Thread Gregory Stark
"Jim Nasby" <[EMAIL PROTECTED]> writes: > The real issue is that the "stock" postgresql.conf is just horrible. It was > originally tuned for something like a 486, but even the recent changes have > only brought it up to the "pentium era" (case in point: 24MB of shared > buffers > equates to a m