Re: BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1

From: Melese Tesfaye <mtesfaye(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1
Date: 2012-09-27 03:01:34
Message-ID: CAJWHPqrQwstK0tc5GGA_C_H7hOkwU9eJvqmCJcKCKUbqWnHX4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks Tom,
I do have a self-contained test case which duplicates the problem. However,
since there are data to be attached and there wasn't a way to attach in the
bug reporting form, I wasn't sure how to proceed.

Would appreciate your assistance.
Thanks again.

On Wed, Sep 26, 2012 at 11:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> mtesfaye(at)gmail(dot)com writes:
> > I had a problem with missing rows in a resultset when using WHERE .. IN
> > after upgrading to 9.2.0.
>
> We'll need a self-contained test case to investigate that. The query
> alone is of no help without table definitions and sample data sufficient
> to reproduce the misbehavior. Since I gather that the table names in
> the query are not even tables but views, what you've provided is even
> more inadequate for investigation.
>
> You can find some advice about submitting useful bug reports at
> https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-09-27 03:17:44 Re: BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1
Previous Message Tom Lane 2012-09-26 23:13:39 Re: BUG #7570: WHERE .. IN bug from 9.2.0 not fixed in 9.2.1