| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | David Teran <david(dot)teran(at)cluster9(dot)com> |
| Cc: | Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Any real known bugs about wrong selects? |
| Date: | 2004-01-13 15:27:09 |
| Message-ID: | 40040E4D.1000104@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> The real question was: are there open known bugs where a select
> statement does not return a correct result, meaning a wrong number of
> rows? Were there a lot of errors like this?
> We are asking this because this makes trouble with the database we are
> currently using. Of course we know that there is no guarantee that
> pgsql works 100% bugfree but we are only asking for user experience.
>
I do not know of any bug such as the one that you are describing. We
have customers doing 240,000 transactaions
and hour with PostgreSQL and have no issues.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-01-13 15:50:35 | Re: Nested transaction workaround? |
| Previous Message | David Teran | 2004-01-13 15:16:28 | Re: Any real known bugs about wrong selects? |