| From: | mtesfaye(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7569: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1 |
| Date: | 2012-09-26 16:25:21 |
| Message-ID: | E1TGuQL-0005q2-3o@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 7569
Logged by: Melese Tesfaye
Email address: mtesfaye(at)gmail(dot)com
PostgreSQL version: 9.2.1
Operating system: Ubuntu 12.04.1 LTS + Debian 6 (both x86_64
Description:
I had a problem with missing rows in a resultset when using WHERE .. IN
after upgrading to 9.2.0. I was about to file a bug report when I found out
that verion 9.2.1 was just released to address the index visibility issue.
I then upgraded to 9.2.1 and followed the instructions for vacuuming and
rebuilding indices
(http://wiki.postgresql.org/wiki/20120924updaterelease#Steps_for_Users_of_PostgreSQL_9.2).
I still missed rows in the resultset. I ended up downgrading to 9.1.5 and it
works just fine without missing rows.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mtesfaye | 2012-09-26 16:31:40 | BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1 |
| Previous Message | Bruce Momjian | 2012-09-26 16:04:04 | Re: BUG #7549: max_connections check should query master when starting standby |