| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | AgentM <agentm(at)themactionfaction(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tsvector/tsearch equality and/or portability issue |
| Date: | 2006-08-24 18:20:55 |
| Message-ID: | 44EDEE07.8090907@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Stefan said he reproduced on OpenBSD/i386 so it is unlikely to be an
> endianness issue. Anyway, here's the comparison code- I guess it doesn't
> use strcmp to avoid encoding silliness. (?)
I suppose that ordering for tsvector type is some strange and it hasn't any
matter. For me, it's a secret why it's needed :)
The reason of bug was: some internal parts of tsvector should be shortaligned,
so there was an unused bytes. Previous comparing function compares they too...
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-08-24 18:27:05 | Re: tsvector/tsearch equality and/or portability issue |
| Previous Message | Stefan Kaltenbrunner | 2006-08-24 17:59:48 | Re: tsvector/tsearch equality and/or portability issue |