| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: UTF8MatchText |
| Date: | 2007-05-18 03:42:45 |
| Message-ID: | 464D20B5.2030104@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Under *no* circumstances use __inline__, as it will certainly break
> every non-gcc compiler. Use "inline", which we #define appropriately
> at need.
>
OK. (this was from upstream patch.)
>
> I thought we'd concluded that this explanation is pseudo-science?
>
>
[...]
>
> spellcheck...
>
>
>
Right. I'm waiting on a consensus about the UTF8-ness of the solution
before I adjust comments.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atul Deopujari | 2007-05-18 03:47:25 | Re: Planning large IN lists |
| Previous Message | Tom Lane | 2007-05-18 03:31:22 | Re: UTF8MatchText |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2007-05-18 04:25:20 | Re: Updateable cursors patch |
| Previous Message | Tom Lane | 2007-05-18 03:31:22 | Re: UTF8MatchText |