Greetings, * Tom Lane (tgl@xxxxxxxxxxxxx) wrote: > Nicholas Chammas <nicholas.chammas@xxxxxxxxx> writes: > > It's only the combination of a) .pgpass and b) RDS auth token that doesn't > > work. This leads me to believe something is going wrong on a code path > > specific to .pgpass, or that there are some undocumented restrictions on > > what can go in .pgpass. > > Looking at the source code, there's a hard-wired restriction that lines of > .pgpass can't be more than 320 characters long (well, NAMEDATALEN*5, but > very few builds don't have NAMEDATALEN=64). I see that somebody very > recently added code to make libpq print a warning for overlength lines, > but I wonder why they didn't just, um, remove the restriction. We had > not previously heard of a use-case for passwords with hundreds of > characters in them, but I guess we need to cope. 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?!" In particular, this seems relevant... https://www.postgresql.org/message-id/29496.1539388920%40sss.pgh.pa.us but I'm also inclined to add support for these longer values. Thanks, Stephen
Attachment:
signature.asc
Description: PGP signature
