possible wierd boolean bug?

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: possible wierd boolean bug?
Date: 2004-12-13 17:07:35
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A7566@Herge.rcsinc.local
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have a strange but reproducible problem where a query does not seem to
return the same results.

esp=# select 1::int4, * from data1.po_line_file
esp-# where pol_po_no = '00000002' and
esp-# (pol_po_no = '00000002' and pol_po_rel_no = 0) and
esp-# (pol_po_no = '00000002' and pol_po_rel_no = 0 and
pol_item_no = '1570')
esp-# limit 1 ;
[fields omitted]
(0 rows)

esp=# select 1::int4, * from data1.po_line_file
esp-# where --pol_po_no = '00000002' and
esp-# --(pol_po_no = '00000002' and pol_po_rel_no = 0) and
esp-# (pol_po_no = '00000002' and pol_po_rel_no = 0 and
pol_item_no = '1570')
esp-# limit 1 ;
[fields omitted, note commented redundant clauses]
(1 row)

The obviously silly Boolean clause here was sql that was generated by a
driver. I recoded the driver to make more intelligent sql and now the
problem is gone, at least from my application. Note that the same query
form but with different tables/fields works correctly 99.99999% of the
time, just not this time...I'm just curious as to how two seemingly
equivalent statements could produce different results...perhpaps I
missed something?

Merlin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message strk 2004-12-13 17:13:29 Re: [postgis-devel] RE: join selectivity
Previous Message Tom Lane 2004-12-13 16:25:29 Re: tuple properties out of TupleTableSlot