Thanks to Tom Lane and to Jan-Benedict Glaw for suggesting
a RAM problem; this has now been confirmed.
I'm relieved that Postgresql does not have what would have
been a very fundamental problem. That's the first time I
find a "bug" which is actually a hardware fault. I guess
sometimes the com
Alain Picard <[EMAIL PROTECTED]> writes:
> Behold!
> select * from test_table
> where data !=''
> and
> data != '';
> -> returns:
>id |
POSTGRESQL BUG REPORT TEMPLATE
Your name : Alain Picard
Your email address : [EMAIL PR
> In article <[EMAIL PROTECTED]>, Alain Picard
><[EMAIL PROTECTED]> writes:
ap> This contrived example is the simplest form I can reproduce the
ap> problem to. My actual application is written in lisp, and uses
ap> unixODBC to talk to postgresql, though I believe the above problem
ap> shou
