Re: timestamp handling in postgres 7.1 behaves strange

pgsql-bugs@postgresql.org writes:
> this works:
> select timestamp (content) from factversionelement where factid=100311 and elementname='newsdate';
>        timestamp
> ------------------------
>  2010-01-02 16:00:00+01
> (1 row)

> this does not:
> select factid from factversionelement where factid=100311 and elementname='newsdate' and timestamp (content) >=
'2001-08-08';
> ERROR:  Bad timestamp external representation 'm'

What this looks like to me is that you have some row in the table that
has content = 'm' rather than a valid timestamp representation, but
does not have (both) factid=100311 and elementname='newsdate'.  You
cannot assume that the WHERE clauses are evaluated in any particular
order.

            regards, tom lane