Обсуждение: connection limit exceeded
Hi Everybody,
On my postgres 8.1.1, I get a response
psql: FATAL: connection limit exceeded for non-superusers
A few questions come to mind...
1) Is this to do with max_connections setting in the postgres
configuration file? (my setting is 100 (I think this is the
default).)
2) how would I look at the "open/used" connections?
3) should I try restarting postgres without changing the setting?
4) what repercussion would there be if I increase this number to,
say, 200? (and would that be a good idea?)
5) finally, what's the best fix? (Do I need to go to pgpool?)
Many thanks in advance.
Regards,
Tena Sakai
tsakai@gallo.ucsf.edu
On Nov 30, 2007 2:55 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote: > On my postgres 8.1.1, I get a response > psql: FATAL: connection limit exceeded for non-superusers > 1) Is this to do with max_connections setting in the postgres > configuration file? (my setting is 100 (I think this is the > default).) Yep. > 2) how would I look at the "open/used" connections? select * from pg_stat_activity; > 3) should I try restarting postgres without changing the setting? Has to be restarted for change to take effect. > 4) what repercussion would there be if I increase this number to, > say, 200? (and would that be a good idea?) A little overhead, nothing bad. > 5) finally, what's the best fix? (Do I need to go to pgpool?) see pgbouncer -- Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com Edison, NJ 08837 | http://www.enterprisedb.com/
Hi Jonah,
Many thanks!
>> 2) how would I look at the "open/used" connections?
> select * from pg_stat_activity;
This is a wonderful view! How would I properly terminate
these (of course there are 99 of them!) these query process?
Should I do this from unix or is there any postgres tool I
can use?
Thank you.
Regards,
Tena Sakai
tsakai@gallo.ucsf.edu
-----Original Message-----
From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
Sent: Fri 11/30/2007 12:03 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Nov 30, 2007 2:55 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> On my postgres 8.1.1, I get a response
> psql: FATAL: connection limit exceeded for non-superusers
> 1) Is this to do with max_connections setting in the postgres
> configuration file? (my setting is 100 (I think this is the
> default).)
Yep.
> 2) how would I look at the "open/used" connections?
select * from pg_stat_activity;
> 3) should I try restarting postgres without changing the setting?
Has to be restarted for change to take effect.
> 4) what repercussion would there be if I increase this number to,
> say, 200? (and would that be a good idea?)
A little overhead, nothing bad.
> 5) finally, what's the best fix? (Do I need to go to pgpool?)
see pgbouncer
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
Edison, NJ 08837 | http://www.enterprisedb.com/
Hi, I also have this issue (I'm using 8.2.4), but whenever this happens I see only a few (4-6) postgresql processes in the system, and my connection limit is set to 128. Kinda strange. Next time when I notice it I will check pg_stat_activity and report back. On Fri, Nov 30, 2007 at 03:03:31PM -0500, Jonah H. Harris wrote: > On Nov 30, 2007 2:55 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote: > > On my postgres 8.1.1, I get a response > > psql: FATAL: connection limit exceeded for non-superusers > > > 1) Is this to do with max_connections setting in the postgres > > configuration file? (my setting is 100 (I think this is the > > default).) > > Yep. > > > 2) how would I look at the "open/used" connections? > > select * from pg_stat_activity; > > > 3) should I try restarting postgres without changing the setting? > > Has to be restarted for change to take effect. > > > 4) what repercussion would there be if I increase this number to, > > say, 200? (and would that be a good idea?) > > A little overhead, nothing bad. > > > 5) finally, what's the best fix? (Do I need to go to pgpool?) > > see pgbouncer > > -- > Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 > EnterpriseDB Corporation | fax: 732.331.1301 > 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com > Edison, NJ 08837 | http://www.enterprisedb.com/ Sincerely, Gergely Czuczy mailto: gergely.czuczy@harmless.hu -- Weenies test. Geniuses solve problems that arise.
Вложения
Hi Jonah,
Many thanks!This is a wonderful view! How would I properly terminate
>> 2) how would I look at the "open/used" connections?
> select * from pg_stat_activity;
these (of course there are 99 of them!) these query process?
Should I do this from unix or is there any postgres tool I
can use?
try pg_cancel_backend(pid)
Thank you.
Regards,-----Original Message-----
From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
Sent: Fri 11/30/2007 12:03 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Nov 30, 2007 2:55 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> On my postgres 8.1.1, I get a response
> psql: FATAL: connection limit exceeded for non-superusers
> 1) Is this to do with max_connections setting in the postgres
> configuration file? (my setting is 100 (I think this is the
> default).)
Yep.
> 2) how would I look at the "open/used" connections?
select * from pg_stat_activity;
> 3) should I try restarting postgres without changing the setting?
Has to be restarted for change to take effect.
> 4) what repercussion would there be if I increase this number to,
> say, 200? (and would that be a good idea?)
A little overhead, nothing bad.
> 5) finally, what's the best fix? (Do I need to go to pgpool?)
see pgbouncer
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
Edison, NJ 08837 | http://www.enterprisedb.com/
--
Usama Munir Dar http://linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar
Many thanks, Jonah!
Tena Sakai
tsakai@gallo.ucsf.edu
-----Original Message-----
From: Jonah H. Harris [mailto:jonah.harris@gmail.com]
Sent: Fri 11/30/2007 1:17 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Nov 30, 2007 3:34 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> This is a wonderful view! How would I properly terminate
> these (of course there are 99 of them!) these query process?
> Should I do this from unix or is there any postgres tool I
> can use?
pg_cancel_backend will cancel a query on them. As for killing the
process itself, use:
kill -TERM
--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
Edison, NJ 08837 | http://www.enterprisedb.com/
Many thanks, Usama!
Tena Sakai
tsakai@gallo.ucsf.edu
-----Original Message-----
From: Usama Dar [mailto:munir.usama@gmail.com]
Sent: Fri 11/30/2007 1:24 PM
To: Tena Sakai
Cc: Jonah H. Harris; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection limit exceeded
On Dec 1, 2007 1:34 AM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> Hi Jonah,
>
> Many thanks!
>
> >> 2) how would I look at the "open/used" connections?
> > select * from pg_stat_activity;
>
> This is a wonderful view! How would I properly terminate
> these (of course there are 99 of them!) these query process?
> Should I do this from unix or is there any postgres tool I
> can use?
>
try pg_cancel_backend(pid)
>
>
> Thank you.
>
> Regards,
>
> Tena Sakai
> tsakai@gallo.ucsf.edu
>
>
>
> -----Original Message-----
> From: Jonah H. Harris [mailto:jonah.harris@gmail.com<jonah.harris@gmail.com>
> ]
> Sent: Fri 11/30/2007 12:03 PM
> To: Tena Sakai
> Cc: pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] connection limit exceeded
>
> On Nov 30, 2007 2:55 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> > On my postgres 8.1.1, I get a response
> > psql: FATAL: connection limit exceeded for non-superusers
>
> > 1) Is this to do with max_connections setting in the postgres
> > configuration file? (my setting is 100 (I think this is the
> > default).)
>
> Yep.
>
> > 2) how would I look at the "open/used" connections?
>
> select * from pg_stat_activity;
>
> > 3) should I try restarting postgres without changing the setting?
>
> Has to be restarted for change to take effect.
>
> > 4) what repercussion would there be if I increase this number to,
> > say, 200? (and would that be a good idea?)
>
> A little overhead, nothing bad.
>
> > 5) finally, what's the best fix? (Do I need to go to pgpool?)
>
> see pgbouncer
>
> --
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Corporation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
> Edison, NJ 08837 | http://www.enterprisedb.com/
>
>
--
Usama Munir Dar http://linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar
On Nov 30, 2007 3:34 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote: > This is a wonderful view! How would I properly terminate > these (of course there are 99 of them!) these query process? > Should I do this from unix or is there any postgres tool I > can use? pg_cancel_backend will cancel a query on them. As for killing the process itself, use: kill -TERM -- Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com Edison, NJ 08837 | http://www.enterprisedb.com/