From: Tom Lane <tgl@sss.pgh.pa.us>
To: jgr@geomaster.pt
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15827: Unable to connect on Windows using pg_services.conf
 using Python psycopg2
In-reply-to: <15827-e6ba53a3a7ed543c@postgresql.org>
References: <15827-e6ba53a3a7ed543c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 31 May 2019 15:57:40 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <82490.1559409563.1@sss.pgh.pa.us>
Date: Sat, 01 Jun 2019 13:19:23 -0400
Message-ID: <82491.1559409563@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I'm using `pg_services.conf` to provide access to a Postgresql database.
> ...
> From other's feedback, I've tried to use the line separators in
> pg_services.conf with \n and \r\n, but the result is the same (because there
> is strange newline after the host address).

Hm, can you double check that?  It sure looks like something is failing to
remove the "\r" from that line of pg_service.conf.  Which is odd, because
libpq opens the file in text mode so the Windows C library ought to take
care of reducing "\r\n" to "\n".

It seems like in general, maybe we ought to trim trailing spaces from
pg_service.conf entries automatically.  But I'm not entirely sure if
that would fix this problem...

			regards, tom lane