| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | David Teran <david(dot)teran(at)cluster9(dot)com>, 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 17:34:14 |
| Message-ID: | Pine.LNX.4.33.0401131032150.22537-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 13 Jan 2004, Joshua D. Drake wrote:
>
> > 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.
IIRC Tom found a bug in the hash indexing that MAY have resulted in short
selects in certain race conditions, but there was no test case to prove
it, and the likelyhood of it happening was really really low.
The last data loss bugs I know of were in the 7.2.x branch and have long
since been stamped out.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Skaryd | 2004-01-13 17:39:47 | pg_catalog permission problem |
| Previous Message | John Sidney-Woollett | 2004-01-13 17:24:11 | Re: Best practice? Web application: single PostgreSQL |