From: | Harold Giménez <harold(at)heroku(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: proposal: hide application_name from other users |
Date: | 2014-01-22 00:52:56 |
Message-ID: | CACZOJr_-WsAwWcH4CwUrb0ZND+2jjxdzN5OKD9Vtxky2ZceC-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 21, 2014 at 4:46 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> * Harold Giménez (harold(at)heroku(dot)com) wrote:
>> This is a separate topic, but in such a case I'd want to know that
>> I've reached max_connections, which may not be a problem if I just
>> don't need any more connections, but I still need something connecting
>> to make sure the service is available at all and can respond to simple
>> SELECT 1 queries and a myriad of other things you'd want to keep track
>> of.
>
> I've never heard of an environment where you can be absolutely confident
> that you need exactly max_connections and zero more. I seriously doubt
> one exists.
>
> The service is not available if only a superuser can connect, imv.
People push the limit all the time. They may run at 80% of their max
and occasionally (and temporarily) scale up to a known bounded level,
but no more.
-Harold
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2014-01-22 00:53:02 | Re: proposal: hide application_name from other users |
Previous Message | Stephen Frost | 2014-01-22 00:46:22 | Re: proposal: hide application_name from other users |