From: Radovan Jablonovsky <radovan.jablonovsky@replicon.com>
To: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: terminating autovacuum process due to administrator command
Date: Mon, 25 Jun 2012 09:00:46 -0600
Message-ID: <CAJYcdTsr++DEra_ttm8yWcKiDHMO7DDO2Lttwp1-e5BN3SmXbg@mail.gmail.com> (raw)
In-Reply-To: <D960CB61B694CF459DCFB4B0128514C208126EEC@exadv11.host.magwien.gv.at>
References: <CAJYcdTtRanwpiBbgbOAgAXRBoV8J7R0gNim4PxV4h7eyb_sAuw@mail.gmail.com>
<D960CB61B694CF459DCFB4B0128514C208126EEC@exadv11.host.magwien.gv.at>
Thanks for response,
How were the connections refused (error message)?
2012-06-13 13:45:38.809 MDT [25172]: [1-1] FATAL: remaining connection
slots are reserved for non-replication superuser connections
2012-06-13 13:45:38.889 MDT [25173]: [1-1] FATAL: remaining connection
slots are reserved for non-replication superuser connections
2012-06-13 13:45:38.895 MDT [25174]: [1-1] FATAL: remaining connection
slots are reserved for non-replication superuser connections
Could it be that there are already max_connections sessions? max_connection
was set to 600, when issue occurred the db server had 85 connection and
server was under medium load.
Server details:
We're running postgres 9.1.1 linux x64 centos 5.8
aspdata=# select version();
version
---------------------------------------------------------------------------------------------------------------
PostgreSQL 9.1.1 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2
20080704 (Red Hat 4.1.2-52), 64-bit
We currently have 1 DB we use for multiple independent tenant schemas. The
database size is current 56227005240 bytes as reported by pg_database_size.
There are 557 schemas each with about 1300 objects (760 tables 520 views).
On Mon, Jun 25, 2012 at 2:03 AM, Albe Laurenz <laurenz.albe@wien.gv.at>wrote:
> Radovan Jablonovsky wrote:
> > Could you please help with this peculiar problem?
> >
> >
> > In PostgreSQL log occurred this message:
> >
> > 2012-06-13 12:58:45.876 MDT [17536]: [1-1] FATAL: terminating
> autovacuum process due to administrator
> > command
> > The server worked for 48 minutes after and then it started refuse
> non-superuser connections, which
> > effectively rendered it unusable for client applications.
> > What could cause this behaviour?
>
> You gave very little information.
>
> How were the connections refused (error message)?
> Could it be that there are already max_connections sessions?
>
> Yours,
> Laurenz Albe
>
--
*Radovan Jablonovsky* | SaaS DBA | Phone 1-403-262-6519 (ext. 256) | Fax
1-403-233-8046****
*
Replicon | Hassle-Free Time & Expense Management Software - 7,300 Customers
- 70 Countries
www.replicon.com | facebook <http://www.facebook.com/Replicon.inc; |
twitter<http://twitter.com/Replicon;
| blog <http://www.replicon.com/blog/; | contact
us<http://www.replicon.com/about_replicon/contact_us.aspx;
We are hiring! | search
jobs<http://tbe.taleo.net/NA2/ats/careers/searchResults.jsp?org=REPLICON&cws=1&act=sort&sortC...;
*
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: radovan.jablonovsky@replicon.com, laurenz.albe@wien.gv.at
Subject: Re: terminating autovacuum process due to administrator command
In-Reply-To: <CAJYcdTsr++DEra_ttm8yWcKiDHMO7DDO2Lttwp1-e5BN3SmXbg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox