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

Re: Changing the default configuration (was Re: [HACKERS] PostgreSQL Benchmarks)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Clift <justin(at)postgresql(dot)org>
Cc: Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>,PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>,pgsql-advocacy(at)postgresql(dot)org
Subject: Re: Changing the default configuration (was Re: [HACKERS] PostgreSQL Benchmarks)
Date: 2003-02-11 17:18:10
Message-ID: 26500.1044983890@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackerspgsql-performance
Justin Clift <justin(at)postgresql(dot)org> writes:
> Personally I'd be a bunch happier if we set the buffers so high that we 
> definitely have decent performance, and the people that want to run 
> PostgreSQL are forced to make the choice of either:
>   1) Adjust their system settings to allow PostgreSQL to run properly, or
>   2) Manually adjust the PostgreSQL settings to run memory-constrained
> This way, PostgreSQL either runs decently, or they are _aware_ that 
> they're limiting it.

Yeah, that is the subtext here.  If you can't increase SHMMAX then you
can always trim the postgresql.conf parameters --- but theoretically,
at least, you should then have a clue that you're running a
badly-configured setup ...

			regards, tom lane

In response to

pgsql-performance by date

Next:From: Josh BerkusDate: 2003-02-11 17:18:48
Subject: Re: Changing the default configuration (was Re:
Previous:From: mlwDate: 2003-02-11 17:12:04
Subject: Re: Changing the default configuration (was Re:

pgsql-hackers by date

Next:From: Josh BerkusDate: 2003-02-11 17:18:48
Subject: Re: Changing the default configuration (was Re:
Previous:From: mlwDate: 2003-02-11 17:12:04
Subject: Re: Changing the default configuration (was Re:

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2003-02-11 17:18:48
Subject: Re: Changing the default configuration (was Re:
Previous:From: mlwDate: 2003-02-11 17:12:04
Subject: Re: Changing the default configuration (was Re:

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