Ian Bicking wrote:
> On Thu, 2002-09-26 at 02:28, Max Ischenko wrote:
> > When requested dataset is too much, something bad is happens and
> > can't figure what it is exactly. It seems like my servlet doesn't
> > notice when DBMS finally finished serving SQL and it continues to
> > wait for something (forever) while postmaster has returned to idle.
> > Moreover, AppServer is lock as well (as I said earilier).
> > Not-so-lengthy requests are handled just fine.
> I don't know Postgres very well, but MySQL lets you limit the size of
> the response by ending your select with "limit 100" (or whatever size).
> I suspect the problem is with the adapter. The Postgres adapters in
> particular seem to have caused lots of problems. I would try doing the
> same query from a simpler Python program, and seeing what happens.
I've misguided you, sorry.
In reality there is not big single queries, but alot of small ones.
For exmaple, gathering information about single Point-of-Sale-Terminal
session requeires issuing ~10 SQL queires which takes about 4 seconds
to comlete. While number of sessions is constrained by id or date all is
fine. But when someone tries to get info about all sessions (> 1000) the
system is choked.
Bst rgrds, M.A.X.: Mechanical Artificial Xenomorph.