From: | "Brett W(dot) McCoy" <bmccoy(at)lan2wan(dot)com> |
---|---|
To: | Brian <signal(at)shreve(dot)net> |
Cc: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] postgres getting slow |
Date: | 1999-05-14 10:54:29 |
Message-ID: | Pine.LNX.4.04.9905140650440.28521-100000@dragosani.lan2wan.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> I noticed that on our postgres server, when more than say 15-20 backends
> are open at once, things start to get real slow. System is:
>
> Redhat 5.2 Linux
> 2.2.8 kernel
> Postgres 6.3.2
> PII 450
> 256MB RAM
>
> Does anyone know why this may be?
Hmmm... I'm trying to optimize Postgres as much as I can right now. I
usually have 4 or 5 backends running, some under CGI and some under ODBC.
I notice the ODBC (via Access) seems to monopolize the database,
especially when doing updates.
> Also I can't seem to get postgres to write to a log about what it is
> doing, whats the best way to get it to do this, so that any
> errors/warnings get logged?
I have something like this in my startup script appended to the invocation
of the postmaster ( as we discussed yesterday):
>> ${PGLOGFILE} 2>&1
where $PGLOGFILE is a path to postgres.log.
Brett W. McCoy
http://www.lan2wan.com/~bmccoy/
-----------------------------------------------------------------------
"One basic notion underlying Usenet is that it is a cooperative."
Having been on USENET for going on ten years, I disagree with this.
The basic notion underlying USENET is the flame.
-- Chuq Von Rospach
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-05-14 12:04:13 | Re: [GENERAL] overwriting large objects bug? |
Previous Message | Stphane Popinet | 1999-05-14 08:36:38 | overwriting large objects bug? |