| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Donald Fraser" <postgres(at)kiwi-fraser(dot)net>, "[BUGS]" <pgsql-bugs(at)postgresql(dot)org>, "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, "Teodor Sigaev" <teodor(at)sigaev(dot)ru> |
| Subject: | Re: Bug with Tsearch and tsvector |
| Date: | 2010-04-27 14:32:12 |
| Message-ID: | 2635.1272378732@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> We'd probably not want to apply this as-is, but should first
>> tighten up what characters URLPath allows, per Kevin's spec
>> research.
> If we're headed that way, I figured I should double-check. The RFC
> I referenced was later obsoleted by:
> http://www.ietf.org/rfc/rfc3986.txt
On reflection, since we're changing the behavior anyway, it seems
like the most defensible thing to do is make the TS parser follow
the RFC's allowed character set exactly. The newer RFC doesn't
restrict '#' so that possible corner case is gone.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-04-27 14:42:12 | Re: Bug with Tsearch and tsvector |
| Previous Message | Kevin Grittner | 2010-04-27 14:22:24 | Re: Bug with Tsearch and tsvector |