| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Dmitrii Golub <dmitrii(dot)golub(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
| Subject: | Re: unexpected result from to_tsvector |
| Date: | 2016-03-20 07:15:49 |
| Message-ID: | CACACo5RtRGm2T2YJmO2DKvvLJYvmFpg5bEW4azFo7shFKTL8_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 20, 2016 01:09, "Dmitrii Golub" <dmitrii(dot)golub(at)gmail(dot)com> wrote:
>
> 2016-03-14 16:22 GMT+03:00 Shulgin, Oleksandr <
oleksandr(dot)shulgin(at)zalando(dot)de>:
>>
>> In fact, the 123-yyy.zzz domain is not valid either according to the RFC
(subdomain can't start with a digit), but since we already allow it, should
we not allow 123_yyy.zzz to be recognized as a Host? Then why not
recognize aaa(at)123_yyy(dot)zzz as an email address?
>>
>> Another option is to prohibit underscore in recognized host names, but
this has more breakage potential IMO.
>>
>
> Alex, actually subdomain can start with digit,
Not according to the RFC you have linked to.
> try it.
What do you mean? Try it with ts_debug()? I already did, you could see me
referring to this example above: 123-yyy.zzz
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-03-20 08:58:08 | Re: Parallel Aggregate |
| Previous Message | Amit Kapila | 2016-03-20 07:01:58 | Re: Patch: fix lock contention for HASHHDR.mutex |