| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, 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-03 17:18:17 |
| Message-ID: | 635718.1599153497@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> This could be refined; in particular, I think that most of the
> password-prompting sites could drop their separate have_password
> flags in favor of checking whether the password pointer is NULL
> or not. That would likely also prove that some of the free(password)
> calls I sprinkled in are unnecessary.
Hearing no objections to this general plan, I went ahead and did that
cleanup. This version seems committable to me.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| remove-password-length-limits-2.patch | text/x-diff | 27.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-03 17:36:58 | Re: Fix for configure error in 9.5/9.6 on macOS 11.0 Big Sur |
| Previous Message | Kasahara Tatsuhito | 2020-09-03 17:18:15 | Re: Get memory contexts of an arbitrary backend process |