| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bugs in planner's equivalence-class processing |
| Date: | 2012-11-02 20:05:36 |
| Message-ID: | CAASwCXdgPkr88zcn4cbW5mEhdAH1kN57gEU=GB8bHpKoXbW8gg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
When I tried our test suite against 9.2.1 one of the tests failed,
it looked really strange, the query had returned a row which could
impossibly match the WHERE statement.
I heard on #postgresql this bug has already been reported.
If helpful, here is a simple test to reproduce the problem:
http://pgsql.privatepaste.com/6429e8a200
From what I understand from the discussion, this "bug" or behaviour
has been around for quite some time, dating back to 7.4,
perhaps not exactly the same in all major versions though.
Would you recommend me to rewrite all queries of this particular
type, where you have COALESCE in the WHERE statement,
as a precaution?
We haven't migrated to 9.2 yet, but perhaps there is a risk
similar queries can render the same problems even in 9.1?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-11-02 20:06:56 | Re: Synchronous commit not... synchronous? |
| Previous Message | Merlin Moncure | 2012-11-02 19:05:47 | Re: Unresolved error 0xC0000409 on Windows Server |