Re: Resource temporarily unavailable

From: "Nico" <nicohmail-postgresql(at)yahoo(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Resource temporarily unavailable
Date: 2004-12-25 23:05:54
Message-ID: cqkroh$qmv$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> schreef in bericht
news:12612(dot)1103945229(at)sss(dot)pgh(dot)pa(dot)us(dot)(dot)(dot)
> "Nico" <nicohmail-postgresql(at)yahoo(dot)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
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message John R Pierce 2004-12-26 00:05:30 Re: Resource temporarily unavailable
Previous Message Tom Lane 2004-12-25 03:27:09 Re: Resource temporarily unavailable