From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-hackers@lists.postgresql.org, Fujii Masao <fujii@postgresql.org>
Subject: Re: Remove line length restriction in passwordFromFile()
Date: Wed, 09 Sep 2020 12:48:17 -0400
Message-ID: <41713.1599670097@sss.pgh.pa.us> (raw)
In-Reply-To: <12eff40e-80df-244e-86b8-c60b0e88bc75@oss.nttdata.com>
References: <4187382.1598909041@sss.pgh.pa.us>
<90aed8c6-a171-4cf7-4e4a-0d4d9593f6c5@oss.nttdata.com>
<b2391bb7-33c5-a25e-e99a-81f7e96efdad@oss.nttdata.com>
<54742.1598973287@sss.pgh.pa.us>
<12eff40e-80df-244e-86b8-c60b0e88bc75@oss.nttdata.com>
Fujii Masao <masao.fujii@oss.nttdata.com> writes:
> The patch was back-patched to v13, but v13 release note still has the following item.
> Tighten libpq's overlength-line handling and comment detection for .pgpass files (Fujii Masao)
> This should be changed to the following or something?
> Teach libpq to handle arbitrary-length lines in .pgpass files (Tom Lane)
Hm. Actually, since that went further back than v13, I don't think
it should appear in the v13 notes at all; it will be material for
the next quarterly update release notes.
We could adjust the release-note entry for your patch to say
"Improve comment detection for .pgpass files", or we could decide
it's not worth documenting that part and just drop the entry.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, masao.fujii@oss.nttdata.com, fujii@postgresql.org
Subject: Re: Remove line length restriction in passwordFromFile()
In-Reply-To: <41713.1599670097@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox