Re: Tightening binary receive functions - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Tightening binary receive functions
Date
Msg-id 407d949e0908310341x4356cb92x6be92e27640a6421@mail.gmail.com
Whole thread Raw
In response to Tightening binary receive functions  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Tightening binary receive functions  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Mon, Aug 31, 2009 at 9:12 AM, Heikki
Linnakangas<heikki.linnakangas@enterprisedb.com> wrote:
> The most notable of these is the change to "char" datatype. The patch
> tightens it so that it no longer accepts values >127 with a multi-byte
> database encoding.

That doesn't sound right to me. We accept casts from integer to "char"
for all values in range (-128..127). The question should be what the
text representation should be since the raw bytes aren't valid mb
encodings.


-- 
greg
http://mit.edu/~gsstark/resume.pdf


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: hot standby - further cleanup of recovery procs stuff
Next
From: Heikki Linnakangas
Date:
Subject: Re: Tightening binary receive functions