pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedpostgres bogged down beyond tolerance
3+ messages / 3 participants
[nested] [flat]
* postgres bogged down beyond tolerance
@ 2007-11-14 17:52 Tena Sakai <tsakai@gallo.ucsf.edu>
2007-11-14 18:35 ` Re: postgres bogged down beyond tolerance Richard Broersma Jr <rabroersma@yahoo.com>
2007-11-15 09:33 ` Re: postgres bogged down beyond tolerance Gregory Stark <stark@enterprisedb.com>
0 siblings, 2 replies; 3+ messages in thread
From: Tena Sakai @ 2007-11-14 17:52 UTC (permalink / raw)
To: pgsql-sql
Hi Everybody,
The postgres server I have (on redhat linux with recent
Dell hardware) is running terribly slow.
A job it should have gotten done in less than 1 hour
took 7.5 hours last night. I checked kernel parameter
shmmax and it was set as 33554432. I "fixed" it as
suggested by the manual:
http://www.postgresql.org/docs/8.2/static/kernel-resources.html
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.
Can somebody please give me a tip, insight as to what I
am missing, doing wrong?
Here's tail of serverlog file in my data directory:
[2007-11-14 08:53:48.062 PST] <gadb 2007-11-14 08:53:36 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 08:53:59.001 PST] <gadb 2007-11-14 08:53:48 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 08:54:10.782 PST] <gadb 2007-11-14 08:53:59 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 08:54:22.557 PST] <gadb 2007-11-14 08:54:10 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 08:54:34.282 PST] <gadb 2007-11-14 08:54:22 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 09:13:36.444 PST] <gadb 2007-11-14 09:13:24 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 09:13:43.637 PST] <gadb 2007-11-14 09:13:32 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 09:17:16.242 PST] <gadb 2007-11-14 09:17:03 PST idle in transaction>LOG: unexpected EOF on client connection
[2007-11-14 09:39:22.841 PST] <gjoslyn 2007-11-14 09:39:22 PST SELECT>ERROR: relation "msysconf" does not exist
[2007-11-14 09:39:22.842 PST] <gjoslyn 2007-11-14 09:39:22 PST SELECT>STATEMENT: SELECT Config, nValue FROM MSysConf
Many thanks in advance.
Regards,
Tena Sakai
tsakai@gallo.ucsf.edu
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: postgres bogged down beyond tolerance
2007-11-14 17:52 postgres bogged down beyond tolerance Tena Sakai <tsakai@gallo.ucsf.edu>
@ 2007-11-14 18:35 ` Richard Broersma Jr <rabroersma@yahoo.com>
1 sibling, 0 replies; 3+ messages in thread
From: Richard Broersma Jr @ 2007-11-14 18:35 UTC (permalink / raw)
To: pgsql-sql@postgresql.org, Tena Sakai <tsakai@gallo.ucsf.edu>
--- On Wed, 11/14/07, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> The postgres server I have (on redhat linux with recent
> Dell hardware) is running terribly slow.
Hello Tena,
If you do not get a response to your question regarding performance, you might try resending this email to : pgsql-performance@postgresql.org .
This mailing list ( pgsql-sql@postgresql.org ) is really intended for discussions of how to construct SQL queries to achieve desired results in a PostgreSQL database.
Regards,
Richard Broersma Jr.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: postgres bogged down beyond tolerance
2007-11-14 17:52 postgres bogged down beyond tolerance Tena Sakai <tsakai@gallo.ucsf.edu>
@ 2007-11-15 09:33 ` Gregory Stark <stark@enterprisedb.com>
1 sibling, 0 replies; 3+ messages in thread
From: Gregory Stark @ 2007-11-15 09:33 UTC (permalink / raw)
To: Tena Sakai <tsakai@gallo.ucsf.edu>; +Cc: pgsql-sql
"Tena Sakai" <tsakai@gallo.ucsf.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!
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2007-11-15 09:33 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-11-14 17:52 postgres bogged down beyond tolerance Tena Sakai <tsakai@gallo.ucsf.edu>
2007-11-14 18:35 ` Richard Broersma Jr <rabroersma@yahoo.com>
2007-11-15 09:33 ` Gregory Stark <stark@enterprisedb.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox