Ok, I will try. I apologize, I made a mistake in the original post:
'J. P. Bickella' returns the correct array and 'J. P. Bickell' returns
NULL. That's what you get for posting in a hurry!
This is the first time I have run this query, so I don't know if it
affects previous versions.
On Mon, Sep 17, 2012 at 9:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> tom(at)tomforb(dot)es writes:
>> I have two queries:
>> The first query returns NULL and the second one returns an int with 623
>> elements in it. The only difference between the two queries is the last
>> string - 'J. P. Bickella' returns NULL and 'J. P. Bickell' returns an
> That's ... bizarre. I assume you were running this same query without
> issues on earlier PG versions? Which?
>> If needed I can host the database this query is executing on for people to
>> download upon request, but it is 1.2gb in size.
> I suspect that you could reproduce the problem with a much smaller
> extract from the table, perhaps a couple thousand rows. Please try
> to create a self-contained test case along those lines --- it'll be
> easier all around than dealing with 1GB of data.
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: McGehee, Robert||Date: 2012-09-17 21:11:40|
|Subject: Incorrect Sort Using Index Scan|
|Previous:||From: Tom Lane||Date: 2012-09-17 20:38:59|
|Subject: Re: BUG #7550: NULL result when coercing a subquery result into an array|