| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
| Cc: | bossartn(at)amazon(dot)com, Stephen Frost <sfrost(at)snowman(dot)net>, isaac(dot)morland(at)gmail(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Maximum password length |
| Date: | 2020-09-01 21:15:20 |
| Message-ID: | 08a13f64-6893-daea-4c51-bcc957809876@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-09-01 02:54, Tom Lane wrote:
> Therefore, I propose setting this up with a #define symbol in
> pg_config_manual.h and leaving it at that. Giving documentation in
> pg_config_manual.h seems sufficient to me. Attached is a revised
> version of Nathan's patches that does it like that.
>
> I set the proposed limit at 1024 bytes, but given that we now know
> of use-cases needing up to 800 bytes, maybe there should be a little
> more headroom? I don't want to make it enormous, though, seeing that
> we're allocating static buffers of that size.
ISTM that it's only going to be a matter of time before that will be
exceeded. Why have a limit at all? Accept whatever StringInfo accepts.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-09-01 21:19:30 | Re: Disk-based hash aggregate's cost model |
| Previous Message | Tomas Vondra | 2020-09-01 21:08:54 | Re: Group by reordering optimization |