Re: Any real known bugs about wrong selects?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: David Teran <david(dot)teran(at)cluster9(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Any real known bugs about wrong selects?
Date: 2004-01-13 16:50:07
Message-ID: 20040113084018.R85596@megazone.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 13 Jan 2004, David Teran wrote:

> I wonder if people encountered bugs like 'a select returns a wrong
> number of rows' or any other very serious bugs. We do not have problems

It's happened on rare occasion in the past in my recollection for things
that are basically bugs. It generally gets resolved quickly and usually
someone can suggest workaround SQL while waiting.

Nominally speaking, some of the case folding issues with identifiers might
be considered to be such a problem: Select * from FOO, "foo" meaning
something different when two tables were created as "FOO" and "foo" from
what the spec would want. This is currently considered a don't do it sort
of situation.

Umm, there are some things that aren't really done yet, for example IIRC
upper()/lower() really only work on single byte encodings. There are
probably other things of this sort that one might need to watch out for.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-01-13 16:51:36 Re: Postgress and MYSQL
Previous Message John Sidney-Woollett 2004-01-13 16:44:33 Re: Best practice? Web application: single PostgreSQL