Re: Increase limit on max length of the password( pg versions < 14)

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: mahendrakar s <mahendrakarforpg(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: Increase limit on max length of the password( pg versions < 14)
Date: 2023-07-18 09:40:31
Message-ID: DCD81154-5960-42CA-A43D-98D51E7EE081@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Jul 2023, at 11:30, mahendrakar s <mahendrakarforpg(at)gmail(dot)com> wrote:

> So we have two options:
> 1. Backport patch[1] to 11,12,13
> 2. Change ONLY the limit on the max length of the password(my patch attached).

We typically only backpatch bugfixes and not functional changes, and this seems
to fall in the latter category.

As the size of the JWT depends on the number of claims in it, are you able to
reduce the number of claims to stay under the limit as a workaround?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2023-07-18 09:58:20 Re: In Postgres 16 BETA, should the ParseNamespaceItem have the same index as it's RangeTableEntry?
Previous Message Amit Kapila 2023-07-18 09:34:35 Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.