Re: Empty SELECT result at simultaneous calls

From: Stefan Wild <wilds81(at)yahoo(dot)de>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Empty SELECT result at simultaneous calls
Date: 2010-09-08 16:01:16
Message-ID: 156556.12045.qm@web26705.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)commandprompt(dot)com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development,
> 24x7 support
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)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 the delays) and I'm not just blaming postgres. Or do you assume other root causes?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bill Moran 2010-09-08 18:35:44 Re: how do i count() similar items
Previous Message Alvaro Herrera 2010-09-08 15:53:56 Re: Empty SELECT result at simultaneous calls