| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | Abhinav Dwivedi <abhinavdwi(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, sakshidhall(at)gmail(dot)com, sakshi(dot)dhall(at)nic(dot)in |
| Subject: | Re: bug in 8.4 and resolved |
| Date: | 2013-04-22 22:05:17 |
| Message-ID: | 5175B41D.5040001@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/21/2013 10:12 PM, Abhinav Dwivedi wrote:
> 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.
What minor version of 8.4 are you using?
>
> Thanks and Regards..
> Abhinav
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2013-04-22 22:13:32 | Re: bug in 8.4 and resolved |
| Previous Message | Adrian Klaver | 2013-04-22 22:00:41 | Re: Need solution for weekly database "snapshot" |