| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Restricting Postgres |
| Date: | 2004-11-03 14:17:43 |
| Message-ID: | 20041103141743.GA15499@phlogiston.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
On Tue, Nov 02, 2004 at 11:52:12PM +0000, 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
Well, you could limit the number of concurrent connections, and set
the query timeout to a relatively low level. What that ought to mean
is that, under heavy load, some queries will abort.
A
--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
When my information changes, I alter my conclusions. What do you do sir?
--attr. John Maynard Keynes
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Randall Smith | 2004-11-03 15:57:24 | Re: oracle synchronization strategy |
| Previous Message | Oliver Elphick | 2004-11-03 13:50:09 | Re: : Unable to load libsqlpg.so |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | stuff | 2004-11-03 17:30:47 | preloading indexes |
| Previous Message | Martin Foster | 2004-11-02 23:52:12 | Restricting Postgres |