Offering tuned config files

OK,

Here's a stab at some extra conf files.  Feel free to shoot them down.

If we can come up with at least _some_ alternative files that we can put
somewhere for them to see when postgres is installed, then at least people
can see what variables will affect what...

I didn't see the point of a 'workstation' option, the default is fine for
that.

Chris


> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Kevin Brown
> Sent: Friday, 14 February 2003 11:26 AM
> To: PostgresSQL Hackers Mailing List; pgsql-advocacy@postgresql.org
> Subject: Re: [HACKERS] Changing the default configuration (was Re:
> [pgsql-advocacy]
>
>
> Josh Berkus wrote:
> > > > Uh ... do we have a basis for recommending any particular sets of
> > > > parameters for these different scenarios?  This could be a good idea
> > > > in the abstract, but I'm not sure I know enough to fill in
> the details.
> >
> > Sure.
> > Mostly-Read database, few users, good hardware, complex queries:
> >     = High shared buffers and sort mem, high geqo and join
> collapse thresholds,
> >         moderate fsm settings, defaults for WAL.
> > Same as above with many users and simple queries (webserver) =
> >     same as above, except lower sort mem and higher connection limit
> > High-Transaction Database =
> >     Moderate shared buffers and sort mem, high FSM settings,
> increase WAL files
> > and buffers.
> > Workstation =
> >     Moderate to low shared buffers and sort mem, moderate FSM,
> defaults for WAL,
> > etc.
> > Low-Impact server = current defaults, more or less.
>
> Okay, but there should probably be one more, called "Benchmark".  The
> real problem is what values to use for it.  :-)
>
>
>
> --
> Kevin Brown                          kevin@sysexperts.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>