Re: Bug #625: bytea data type problem/bug - Mailing list pgsql-bugs

From Joe Conway
Subject Re: Bug #625: bytea data type problem/bug
Date
Msg-id 3CA2395C.7080403@joeconway.com
Whole thread Raw
In response to Bug #625: bytea data type problem/bug  (pgsql-bugs@postgresql.org)
List pgsql-bugs
pgsql-bugs@postgresql.org wrote:
> Eric Lu (yclu@ecompliance.net) reports a bug with a severity of 4
> The lower the number the more severe it is.
>
> Short Description
> bytea data type problem/bug
>
> Long Description
> Hi,
>
> It happens when I was trying to test the avalaibility of the new binary data type <bytea> comes with ver 7.2.
> As I read from the document, <bytea> will take data from '\\000' (0d)to '\\377' (255d). Although it saves data more
thanone byte, it looks odd to me that the first digit of the binary data could never be greater than '3'. 
> Is it the way it should be?
> Thanks!
>
> Eric Lu
>

The escaped values must be three-digits, octal (i.e. base 8) numbers,
and in the range of 0 - 255 in decimal (base 10). Only the digits 0 - 7
are defined, and 377 octal == 255 decimal is the maximum allowable
value. Anything starting with 4 - 7 (e.g. 400 octal == 256 decimal) is
too big.

Joe

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #625: bytea data type problem/bug
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #626: Query with View not returning proper results