回复: Re: A documents mistaken of PG12.5

From: "qiuchenjun(at)highgo(dot)com" <qiuchenjun(at)highgo(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: 回复: Re: A documents mistaken of PG12.5
Date: 2020-12-01 01:59:46
Message-ID: 2020120109594563250511@highgo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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(at)highgo(dot)com

发件人: Heikki Linnakangas
发送时间: 2020-11-30 17:02
收件人: qiuchenjun(at)highgo(dot)com; pgsql-bugs
主题: Re: A documents mistaken of PG12.5
On 30/11/2020 04:50, qiuchenjun(at)highgo(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2020-12-01 02:48:31 Re: BUG #16663: DROP INDEX did not free up disk space: idle connection hold file marked as deleted
Previous Message James Coleman 2020-12-01 00:43:58 Re: segfault with incremental sort