Re: Empty SELECT result at simultaneous calls - Mailing list pgsql-general

From Stefan Wild
Subject Re: Empty SELECT result at simultaneous calls
Date
Msg-id 156556.12045.qm@web26705.mail.ukl.yahoo.com
Whole thread Raw
In response to Re: Empty SELECT result at simultaneous calls  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
> Excerpts from Stefan Wild's message
> of mié sep 08 11:40:25 -0400 2010:
> > Hello,
> >
> > as already stated: "When I'm working with delays in
> the servlets, everything works fine." the same selects on
> the same id work fine if delayd. So the data should not be
> the problem.
>
> So why are you blaming Postgres?
>
> --
> Álvaro Herrera <alvherre@commandprompt.com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development,
> 24x7 support
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

In my opinion this is a performance problem (HW + SW). So my question is: how can I improve the situation (beside using
thedelays) and I'm not just blaming postgres. Or do you assume other root causes? 




pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Empty SELECT result at simultaneous calls
Next
From: jackassplus
Date:
Subject: how do i count() similar items