Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, adam(at)labkey(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Date: 2024-12-11 22:39:35
Message-ID: CA+hUKGK+CJAdixbROOTc78jqOB+tZO0XeeDw0xemYJUBHQoxVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Dec 12, 2024 at 9:59 AM Nathan Bossart <nathandbossart(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2024-12-11 22:40:38 Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
Previous Message Niklas Hambüchen 2024-12-11 21:59:41 "memory exhausted" in query parser/simplifier for many nested parentheses