Re: Feature Request: Extending PostgreSQL's Identifier Length Limit

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: David HJ <chuxiongzhong(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Feature Request: Extending PostgreSQL's Identifier Length Limit
Date: 2024-08-19 01:17:38
Message-ID: ZsKdMvP20lFIhda-@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 18, 2024 at 11:45:45AM +0200, Álvaro Herrera wrote:
> On 2024-Jul-18, David HJ wrote:
>
> > As a long-time PostgreSQL user, I've increasingly run into issues with the
> > 63-byte limit for identifiers, particularly table names. This limit, while
> > historically sufficient, is becoming a significant pain point in modern
> > database design and usage.
>
> This has been discussed before. I think the latest discussion, and some
> preliminary proof-of-concept patches, were around here:
>
> https://postgr.es/m/CAFBsxsF2V8n9w0SGK56bre3Mk9fzZS=9aaA8Gfs_n+woa3Dr-Q@mail.gmail.com

FYI, the COMMENT ON command can help to document identifiers.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-08-19 01:38:55 Re: Cirrus CI for macOS branches 16 and 15 broken
Previous Message Thomas Munro 2024-08-19 00:53:09 Re: Cirrus CI for macOS branches 16 and 15 broken