From: | Steve Lane <slane(at)moyergroup(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: RAM usage per connection |
Date: | 2004-05-13 00:15:43 |
Message-ID: | BCC80C3F.10FC2%slane@moyergroup.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Date: Wed, 12 May 2004 16:13:37 -0400
> To: Steve Lane <slane(at)moyergroup(dot)com>
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] RAM usage per connection
>
> Steve Lane <slane(at)moyergroup(dot)com> writes:
>> I have a customer with an application in production (postgres + php +
>> apache) where we began seeing a number of scary messages in the logs. (It's
>> postgres 7.2.1, by the way).
> ^^^^^^^^^^^^^^
>
> Reading the CVS logs for post-7.2.1 bug fixes will curl your toes.
> You're irresponsible to still be running production data on that
> version. Move up to 7.2.4 before you find out the hard way.
I spoke too hastily. It's 7.1.3. Which probably doesn't make it better :-(
>
>> I tried increasing max_clients, but got a message to the effect that SHMMIN
>> was set incorrectly on my machine ...
>
> I'd expect SHMMAX to be the issue not SHMMIN. It's set very
> conservatively on many platforms, and you should not be afraid to raise
> it.
I was also puzzled to see the reference to SHMMIN. I'll look again.
-- steve
From | Date | Subject | |
---|---|---|---|
Next Message | Laurens Wagemakers | 2004-05-13 07:23:50 | GNUmakefile size 0 |
Previous Message | Jie Liang | 2004-05-12 23:40:06 | Re: [SQL] \set |