Hi,
There are few query I found at the time of monitoring below
00:54:43.574338 | 26952 | select a.actno,MAX(b.actid) as
actid,MAX(b.actname) as name,MAX(b.phone) as phone,MAX(b.email) as
mail,MAX(a.subsno) as subs,MAX(t.pkgid
) as svcid,MAX(a.expirydt) as expirydt,MAX(d.domid) as
domid,MAX(
On Wed, Nov 14, 2012 at 2:30 AM, Aaron Bono wrote:
> On our old server, our hosting company said the server was running out of
> RAM and then became unresponsive. I haven't checked about the new server
> yet.
Unresponsive how? Can you ssh to it? Can you log to Postgres?
For how long does it ha
Hi,
I've been searching the web and reviewing documentation, but I cannot find
any reference to whether or not a parameter, for example,
failed_login_attempts, exists in PostgreSQL that determines the number of
attempts a user can make before being locked. In addition, if such a
parameter or
On our old server, our hosting company said the server was running out of
RAM and then became unresponsive. I haven't checked about the new server
yet.
I noticed our problems started about the time when we loaded a new client
into the database that had nearly 1 GB of large files stored in BLOBs -
Aaron Bono wrote:
> (there are currently a little over 200 active connections to the
> database):
How many cores do you have on the system? What sort of storage
systeme? What, exactly, are the symptoms of the problem? Are there
200 active connections when the problem occurs? By "active", do you
m