Re: Resource temporarily unavailable
От | Nico |
---|---|
Тема | Re: Resource temporarily unavailable |
Дата | |
Msg-id | cqkroh$qmv$1@news.hub.org обсуждение исходный текст |
Ответ на | Resource temporarily unavailable ("Nico" <nicohmail-postgresql@yahoo.com>) |
Ответы |
Re: Resource temporarily unavailable
|
Список | pgsql-jdbc |
The kernel is 2.4.21-15.0.2.ELsmp. Don't know which Linux distribution, since it's a remote server. So you think, I should keep the connection open the whole time until the servlet is finished, instead of opening and closing it everytime I need it? "Tom Lane" <tgl@sss.pgh.pa.us> schreef in bericht news:12612.1103945229@sss.pgh.pa.us... > "Nico" <nicohmail-postgresql@yahoo.com> writes: >> topframe gets data from two tables, so does the left and the right. They >> each make a connection and a resultset for each (6 of them) query based >> on >> those tables. Additionally, they use a common table for metadata. >> After a few refreshes(three or four), he gives me an error: resource >> temporarily unavailable. How can I resolve this issue? > > I think you're running into a processes-per-user limit, preventing the > postmaster from spawning more backend processes. You can and should > raise that limit (see your kernel documentation for details --- without > knowing what platform you're running on, I can't help). But you should > also rethink the strategy of opening a separate database connection for > each individual query. The overhead of doing things that way is > enormous. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >
В списке pgsql-jdbc по дате отправления: