On Dec 1, 2007 1:34 AM, Tena Sakai <[EMAIL PROTECTED]> 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 > [EMAIL PROTECTED] > > > > -----Original Message----- > From: Jonah H. Harris [mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]> > ] > 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 <[EMAIL PROTECTED]> 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 | [EMAIL PROTECTED] > Edison, NJ 08837 | http://www.enterprisedb.com/ > > -- Usama Munir Dar http://linkedin.com/in/usamadar Consultant Architect Cell:+92 321 5020666 Skype: usamadar
