Re: unexpected result from to_tsvector - Mailing list pgsql-hackers

From Shulgin, Oleksandr
Subject Re: unexpected result from to_tsvector
Date
Msg-id CACACo5Ry+HjDWHP0jLGwao9GwRihRGW38ra9iEowZSMRV5_oog@mail.gmail.com
Whole thread Raw
In response to Re: unexpected result from to_tsvector  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: unexpected result from to_tsvector
List pgsql-hackers
On Sun, Mar 20, 2016 at 3:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de> writes:
> On Mar 20, 2016 01:09, "Dmitrii Golub" <dmitrii.golub@gmail.com> wrote:
>> Alex, actually subdomain can start with digit,

> Not according to the RFC you have linked to.

The powers-that-be relaxed that some time ago; I assume there's a newer
RFC.  For instance, "163.com" is a real domain:

$ dig 163.com
...
;; QUESTION SECTION:
;163.com.                       IN      A

Hm, indeed.   Unfortunately, it is not quite easy to find "the" new RFC, there was quite a number of correcting and extending RFCs issued over the last (almost) 30 years, which is not that surprising...

Are we going to do something about it?  Is it likely that relaxing/changing the rules on our side will break any possible workarounds that people might have employed to make the search work like they want it to work?

--
Alex

pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: [PROPOSAL] Client Log Output Filtering
Next
From: Alvaro Herrera
Date:
Subject: Re: Some messages of pg_rewind --debug not getting translated