Mark Dilger <pgsql(at)markdilger(dot)com> writes:
>> pgsql=# select chr(14989485);
>> (1 row)
Is there a principled rationale for this particular behavior as
opposed to any other?
In particular, in UTF8 land I'd have expected the argument of chr()
to be interpreted as a Unicode code point, not as actual UTF8 bytes
with a randomly-chosen endianness.
Not sure what to do in other multibyte encodings.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2007-04-02 22:46:15|
|Subject: Re: [HACKERS] timestamp subtraction (was Re: formatting
intervals with to_char)|
|Previous:||From: Bruce Momjian||Date: 2007-04-02 22:29:15|
|Subject: Re: [PATCHES] pg_standby|