Re: prevent invalidly encoded input - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: prevent invalidly encoded input
Date
Msg-id 46E74830.2070901@dunslane.net
Whole thread Raw
In response to Re: prevent invalidly encoded input  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: prevent invalidly encoded input  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches

Tom Lane wrote:
> Also, I'd kinda like to have the check-for-high-bit optimization in
> scan.l too --- some people do throw big literals at the thing.
>
>
>
OK, will do. Am I correct in thinking I don't need to worry about the
<xeescape> case, only the <xeoctesc> and <xehexesc> cases?

cheers

andrew

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: HOT documentation README
Next
From: ITAGAKI Takahiro
Date:
Subject: Version in Japanese FAQ is wrong (was [COMMITTERS] pgsql: Stamp releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20.)