From: qiuchenjun@highgo.com <qiuchenjun@highgo.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: 回复: Re: A documents mistaken of PG12.5
Date: Tue, 1 Dec 2020 09:59:46 +0800
Message-ID: <2020120109594563250511@highgo.com> (raw)
References: <202011301050138117195@highgo.com>
<1cc5b81b-1c91-423c-be59-d0169404e796@iki.fi>
Hi Heikki,
Thank you very much.You are right.
I think I'm confusing the two syntax.
I think I need a deeper understanding and operation.
祝工作顺利!
-------------------------------------------
邱臣君
瀚高基础软件股份有限公司
网址:www.highgo.com
地址:济南市高新区新泺大街2117号铭盛大厦20层
手机:186-6081-2363 邮箱:qiuchenjun@highgo.com
发件人: Heikki Linnakangas
发送时间: 2020-11-30 17:02
收件人: qiuchenjun@highgo.com; pgsql-bugs
主题: Re: A documents mistaken of PG12.5
On 30/11/2020 04:50, qiuchenjun@highgo.com wrote:
> Hello,
>
> I found the mistaken in the PG12.5,chapter 4.1.2.2
> whereas in chapter 4.1.1
>
> I think 6-digit is right.
It seems correct to me as it is. Chapter 4.1.1 talks about this syntax:
postgres=# select U&'d\0061t\+000061';
?column?
----------
data
(1 row)
Whereas chapter 4.1.2.2 talks about this syntax:
postgres=# select E'd\u0061t\U00000061';
?column?
----------
data
(1 row)
The former indeed uses 6 digits, whereas the latter uses 8 digits.
- Heikki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: qiuchenjun@highgo.com, hlinnaka@iki.fi, pgsql-bugs@lists.postgresql.org
Subject: Re: 回复: Re: A documents mistaken of PG12.5
In-Reply-To: <2020120109594563250511@highgo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox