From: | "Len Morgan" <len-morgan(at)crcom(dot)net> |
---|---|
To: | "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: refusing connections based on load ... |
Date: | 2001-04-23 22:20:36 |
Message-ID: | 004d01c0cc43$9ff23660$0908a8c0@H233.bstx.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>Nathan Myers wrote:
>> On Mon, Apr 23, 2001 at 03:09:53PM -0300, The Hermit Hacker wrote:
>> >
>> > Anyone thought of implementing this, similar to how sendmail does it?
If
>> > load > n, refuse connections?
>> > ...
>> > If nobody is working on something like this, does anyone but me feel
that
>> > it has merit to make use of? I'll play with it if so ...
>>
>> I agree that it would be useful. Even more useful would be soft load
>> shedding, where once some load average level is exceeded the postmaster
>> delays a bit (proportionately) before accepting a connection.
>
> Or have the load check on AtXactStart, and delay new
> transactions until load is back below x, where x is
> configurable per user/group plus some per database scaling
> factor.
How is this different than limiting the number of backends that can be
running at once? It would seem to me that a user that has a "delayed"
startup is going to think there's something wrong with the server and keep
trying, where as a message like "too many clients - try again later"
explains what's really going on.
len morgan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-04-23 23:43:05 | Re: concurrent Postgres on NUMA - howto ? |
Previous Message | Peter Eisentraut | 2001-04-23 21:20:23 | Re: SET SESSION AUTHORIZATION (was Re: Real/effective user) |