Re: Empty SELECT result at simultaneous calls

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Stefan Wild <wilds81(at)yahoo(dot)de>
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 15:53:56
Message-ID: 1283961209-sup-6270@alvh.no-ip.org
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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Wild 2010-09-08 16:01:16 Re: Empty SELECT result at simultaneous calls
Previous Message Stefan Wild 2010-09-08 15:40:25 Re: Empty SELECT result at simultaneous calls