Subject: Re: Amazon RDS auth tokens in .pgpass
To: pgsql-admin@lists.postgresql.org
References: 
 <CAOhmDze1nqG2vfegpSsTFCgaiFRsqgjO6yLsbmhroz2zGmJHog@mail.gmail.com>
 <4119486.1598897040@sss.pgh.pa.us>
 <20200831181648.GT29590@tamriel.snowman.net>
 <4123590.1598898063@sss.pgh.pa.us>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <8c791ff3-3f48-99dc-4d33-cab8701d0997@gmail.com>
Date: Mon, 31 Aug 2020 13:26:23 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <4123590.1598898063@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 8/31/20 1:21 PM, Tom Lane wrote:
> Stephen Frost <sfrost@snowman.net> writes:
>> My memory might be faulty, but I've got some specific recollection of
>> people complaining about this before and the community response being
>> "who would ever need such very long things?!"
> Yeah, so I guessed wrong ;-).  Never too late to absorb new facts though.
>
> That thread does point out that passwordFromFile() is far from the
> only place that assumes passwords aren't going to be longer than
> what would be sane to enter manually.  I wonder whether we need to
> worry about the other bottlenecks.

Would it be better to add a .pgtoken file which gets examined (and bypasses 
those other length restrictions) if the user isn't in .pgpass?  Or is that a 
feature which would have to wait for v14?

-- 
Angular momentum makes the world go 'round.