bug in 8.4 and resolved - Mailing list pgsql-general

From Abhinav Dwivedi
Subject bug in 8.4 and resolved
Date
Msg-id CAFF6oqSqvd64zxz6wLhkgq9Zfzjc1h0NQZ57ZNv-=1jLdVT0JQ@mail.gmail.com
Whole thread Raw
Responses Re: bug in 8.4 and resolved
Re: bug in 8.4 and resolved
List 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

pgsql-general by date:

Previous
From: Steven Schlansker
Date:
Subject: Re: pg_restore from split files
Next
From: Adrian Klaver
Date:
Subject: Re: Need solution for weekly database "snapshot"