Re: ILIKE + OR fault - propably a memory leak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michał Pasternak <doc(at)lublin(dot)t1(dot)pl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: ILIKE + OR fault - propably a memory leak
Date: 2001-09-06 16:47:54
Message-ID: 2698.999794874@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?iso-8859-2?Q?Micha=B3?= Pasternak <doc(at)lublin(dot)t1(dot)pl> writes:
> Micha Pasternak [Thu, Sep 06, 2001 at 12:25:24PM +0200]:
>> But this doesn't (and I need it to work):
>>
>> TYTUL_OR ILIKE 'Ocena%' OR TITLE LIKE 'Ocena%';
>> TYTUL_OR LIKE 'Ocena%' or TITLE LIKE 'Ocena%';

> Uh, I forgot: server starts to output something, which looks like a one row,
> one-field result with infinite length. It contains trashed values of normal
> output columns.

I don't see any such problem here, and I really doubt that the LIKE has
anything to do with it. Possibly you've got corrupted data in a row
of that table that is selected by this query and not other queries?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Larry Rosenman 2001-09-06 18:34:21 cvs tip: gmake breakage.
Previous Message Bruce Momjian 2001-09-06 16:11:30 Re: Using nulls with earthdistance operator crashes backend