From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Martin Foster <martin(at)ethereal-realms(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Restricting Postgres |
Date: | 2004-11-03 19:21:24 |
Message-ID: | 1099509684.4320.2.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Tue, 2004-11-02 at 23:52, Martin Foster wrote:
> Is there a way to restrict how much load a PostgreSQL server can take
> before dropping queries in order to safeguard the server? I was
> looking at the login.conf (5) man page and while it allows me to limit
> by processor time this seems to not fit my specific needs.
>
> Essentially, I am looking for a sort of functionality similar to what
> Sendmail and Apache have. Once the load of the system reaches a
> certain defined limit the daemon drops tasks until such a time that it
> can resume normal operation.
Sounds great... could you give more shape to the idea, so people can
comment on it?
What limit? Measured how? Normal operation is what?
Drop what? How to tell?
>
> While not necessarily common on my servers I have witnessed some fairly
> high load averages which may have led to the machine dropping outright.
> Any help on this matter would be appreciated.
You can limit the number of connections overall?
--
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Strickland | 2004-11-03 19:34:03 | Re: PostgreSQL on Linux PC vs MacOS X |
Previous Message | Bruce Momjian | 2004-11-03 19:20:06 | Re: pg_xlog |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2004-11-03 19:35:28 | Re: preloading indexes |
Previous Message | Doug Y | 2004-11-03 19:17:52 | Re: vacuum analyze slows sql query |