Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Date
Msg-id CA+hUKGK+CJAdixbROOTc78jqOB+tZO0XeeDw0xemYJUBHQoxVg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-bugs
Tree view 
On Thu, Dec 12, 2024 at 9:59 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
> If we are leaning towards a more comprehensive fix in v18, ISTM we should
> go ahead and revert commit 562bee0 (both for master and v17).  Or am I
> misinterpreting the proposed path forward here?

Yeah.  Just to confirm, the CLUSTER ENCODING concept is definitely
future-release-only material

pgsql-bugs by date:

Previous
From: Niklas Hambüchen
Date:
Subject: "memory exhausted" in query parser/simplifier for many nested parentheses
Next
From: Tom Lane
Date:
Subject: Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'