> "Korea PostgreSQL Users' Group" <pgsql-kr(at)postgresql(dot)or(dot)kr> writes:
> >> Hm. I don't think it can actually fail, because the wchar strings are
> >> zero-terminated.
> > [ yes it can ]
> You're right. I was confused at first because I couldn't reproduce the
> problem, but then I realized it's because I'm running with
> CLOBBER_FREED_MEMORY enabled, so the junk beyond the end of the string
> won't match the other string.
> Will commit the patch. Thanks.
> regards, tom lane
It's surprising that nobody noticed the bug until now. It seems it has
been there since 7.3 days. I would like to make a back patch for
7.3-stable if nobody objects.
BTW, I'm interested in Korea PostgreSQL Users' Group since I myself am
a bord member of Japan PostgreSQL Users' Group. Please let me know if
both users group could make some collaboration, such as having a
seminar in Korea or in Japan.
In response to
pgsql-hackers by date
|Next:||From: Kevin Brown||Date: 2004-01-31 03:35:52|
|Subject: Re: index scan with functional indexes -- solved|
|Previous:||From: Dan Langille||Date: 2004-01-31 02:10:55|
|Subject: dump + restore didn't include schemas|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2004-01-31 04:36:37|
|Subject: Re: [PATCHES] v7.4.1 text_position() patch |
|Previous:||From: Tom Lane||Date: 2004-01-30 23:06:06|
|Subject: Re: v7.4.1 text_position() patch |