Re: Comments in .pgpass file...

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Erik Wienhold <ewie(at)ewie(dot)name>
Cc: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Comments in .pgpass file...
Date: 2024-05-21 01:24:07
Message-ID: CAKFQuwY=5_rReQ9dW7gh_ivuSGKg6F4G=O6y1ruCg4zB0svKjA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Monday, May 20, 2024, Erik Wienhold <ewie(at)ewie(dot)name> wrote:

> On 2024-05-21 03:01 +0200, Ron Johnson wrote:
> > It seems that psql (or maybe libpq) doesn't like trailing comments.
> >
> > This works:
> > 10.143.170.206:5432:*:11026270:Blarge
> >
> > But this does not:
> > 10.143.170.206:5432:*:11026270:Blarge # Host name: fubar
>
> How should libpq know where the password ends and the comment begins
> while still accepting passwords that contain "#"? The password is
> everything between the 4th unescaped colon and the end of line.
>
> This could be made explicit in the docs. But the docs don't even say
> that you can put entries and comments one the same line.
>

As written the docs say if your password contain : or \ you should escape
that character with a \ …

I’m not that surprised that a reader expected the password to end at the
first space.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Erik Wienhold 2024-05-21 01:44:02 Re: Comments in .pgpass file...
Previous Message Erik Wienhold 2024-05-21 01:18:14 Re: Comments in .pgpass file...