Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version
Date
Msg-id d6a0d674-90c4-4295-bc1c-f4cddeab35b3@eisentraut.org
Whole thread Raw
In response to Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view 
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.

pgsql-general by date:

Previous
From: Eugen Konkov
Date:
Subject: A question about possible recovery inconsistency
Next
From: Tom Lane
Date:
Subject: Re: Proposal to Compile a 256-Byte Identifier Length Version Alongside the Current 64-Byte Version