From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
---|---|
To: | "Zechman, Derek S" <Derek(dot)S(dot)Zechman(at)snapon(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_hba.conf "authentication file token too long, skipping" |
Date: | 2023-08-02 16:20:29 |
Message-ID: | 46011cbb-74e0-4e7d-9a78-b7857cc62918@app.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 1, 2023, at 1:29 PM, Zechman, Derek S wrote:
> " A one-line improvement would be to increase that constant, but it doesn't look very much harder to get rid of that fixed-size buffer altogether in favor of a StringInfo."
>
> Is this something that can be included in the next patch?
Tom pushed patches for all supported back branches that raises the token length
from 256 to 10240 [1]. If it is a v13 or earlier [2], it also requires to
change the limit of line length (from 8192 to 20480). In v16 this limit was
completely eliminated using StringInfo [3].
In summary, this improvement will be available in the next minor releases.
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=313ceda2fe2ee8dd903ad4773f54de14807807c6
[2] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=0660f74e861d0dc942af3e0b5f88cb2f0c72aee5
[3] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=de3f0e3fe0e7d44620111c5723504a3a6e8c046e
--
Euler Taveira
EDB https://www.enterprisedb.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2023-08-02 16:29:54 | Re: BUG #18045: NpgSQL installation not working |
Previous Message | Andrey M. Borodin | 2023-08-02 08:34:17 | Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1 |