bug in 8.4 and resolved

From: Abhinav Dwivedi <abhinavdwi(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: sakshidhall(at)gmail(dot)com, sakshi(dot)dhall(at)nic(dot)in
Subject: bug in 8.4 and resolved
Date: 2013-04-22 05:12:19
Message-ID: CAFF6oqSqvd64zxz6wLhkgq9Zfzjc1h0NQZ57ZNv-=1jLdVT0JQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dear Member,

We found a bug in postgresql 8.4 details are follows.

If a syntactically wrong query is made inner query of a nested query then
the whole query wrongly returns a dataset instead of an error message. For
example:

select * from district where statecode in (Select districtcode from state)

Please note that the attribute districtcode is not existent in the table
state and if this query i.e. Select districtcode from state is executed in
isolation then it correctly throws an error message. But when this
incorrect query is made inner query of a nested query then the whole query
wrongly returns a dataset.

This issue is observed on Postgres8.4 and is found resolved on Postgres9.1.
But our issue is that our application is using postgres8.4. Where to
upgrade is not possible in quick time .so is there a possible fix (patch
etc.. ) for this on Postgres8.4 itself.

Thanks and Regards..
Abhinav

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2013-04-22 07:09:16 Re: Implementing DB2's "distinct" types
Previous Message Adrian Klaver 2013-04-21 20:07:49 Re: Memory usage after upgrade to 9.2.4