Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, David HJ <chuxiongzhong(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version
Date: 2023-10-11 05:53:53
Message-ID: d6a0d674-90c4-4295-bc1c-f4cddeab35b3@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10.10.23 08:22, Laurenz Albe wrote:
> Apart from that, it is a good idea to use table names that are standard
> SQL identifiers, so that you don't have to double quote them all the time.

FWIW, the Chinese character sequences posted here would be valid
unquoted identifiers if PostgreSQL implemented standard SQL
correctly/completely.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2023-10-11 05:56:54 Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version
Previous Message Eugen Konkov 2023-10-10 15:46:11 A question about possible recovery inconsistency