From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu> |
Cc: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: postgres bogged down beyond tolerance |
Date: | 2007-11-15 09:33:27 |
Message-ID: | 87wssjx388.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu> writes:
> Namely, I shutdown the database, issued two commands:
> /sbin/sysctl -w kernel.shmmax=134217728
> /sbin/sysctl -w kernel.shmall=2097152
> and rebooted the computer.
>
> After it came up, I checked the shmmax and it is set
> as 33554432. Which surprised me. Since I used -w
> flag, I thought it should've written to /etc/sysctl.conf,
> but there is no such entry at all and the data of this
> file is from 2006.
sysctl changes the values for the running kernel. /etc/sysctl is a file you
edit manually to tell the boot scripts what values to store (using sysctl) so
you don't have to run sysctl every time you reboot.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
From | Date | Subject | |
---|---|---|---|
Next Message | Sabin Coanda | 2007-11-15 13:45:20 | trap for any exception |
Previous Message | Richard Broersma Jr | 2007-11-14 18:35:15 | Re: postgres bogged down beyond tolerance |