| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | mahendrakar s <mahendrakarforpg(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Increase limit on max length of the password( pg versions < 14) |
| Date: | 2023-07-18 14:50:49 |
| Message-ID: | 46805.1689691849@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vik Fearing <vik(at)postgresfriends(dot)org> writes:
> On 7/18/23 11:30, mahendrakar s wrote:
>> We have encountered an issue (invalid message length) when the
>> password length is > 1000 in pg 11,12,13 versions.
> The third option is to upgrade.
Yeah. I don't see any good reason to consider this behavior change as
something other than a new feature. Also, the proposed patch is
effectively cherry-picking one single line of the combined effect of
two rather large patches (67a472d71 and 9626325da). I'm unconvinced
that it does very much of use without the rest of those patches; but
we are most certainly not back-patching 67a472d71.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2023-07-18 14:59:32 | Giving more detail in pg_upgrade errormessage |
| Previous Message | Alena Rybakina | 2023-07-18 14:25:28 | Re: POC, WIP: OR-clause support for indexes |