Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1hXA34-0000zg-OX
	for pgsql-bugs@arkaria.postgresql.org; Sat, 01 Jun 2019 19:52:15 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1hXA33-0000sd-7Z
	for pgsql-bugs@arkaria.postgresql.org; Sat, 01 Jun 2019 19:52:13 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <ipluta@wp.pl>)
	id 1hXA32-0000rh-OQ
	for pgsql-bugs@lists.postgresql.org; Sat, 01 Jun 2019 19:52:12 +0000
Received: from mx4.wp.pl ([212.77.101.12])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <ipluta@wp.pl>)
	id 1hXA30-0004Ll-H8
	for pgsql-bugs@lists.postgresql.org; Sat, 01 Jun 2019 19:52:12 +0000
Received: (wp-smtpd smtp.wp.pl 1434 invoked from network);
 1 Jun 2019 21:52:07 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wp.pl; s=1024a;
          t=1559418727; bh=0Fa485AxMrgh7Um3yR/5skOcvdORrOhRQSOSqVQuO3w=;
          h=Subject:To:From;
          b=l1ZDTp4i8Z56Xo8q/v5cJtfwOshh936tfYrZYhimDO9cJRXFfAFcpiWbym0MZzx0L
           gZlr/DPYTVdbUqeIGTP5Ks5K0B/4vzZ3LrTrZe10N6KY5ehGtfOcE8P8/LY2vGl1qW
           vgSuMme6cOkAF25bSVW3GTJ3910yStX9BbtL9DXE=
Received: from bhp205.neoplus.adsl.tpnet.pl (HELO [10.0.0.84])
 (ipluta@wp.pl@[83.28.105.205])
          (envelope-sender <ipluta@wp.pl>)
          by smtp.wp.pl (WP-SMTPD) with ECDHE-RSA-AES256-GCM-SHA384 encrypted
 SMTP
          for <noreply@postgresql.org>; 1 Jun 2019 21:52:07 +0200
Subject: Re: BUG #15827: Unable to connect on Windows using pg_services.conf
 using Python psycopg2
To: jgr@geomaster.pt, pgsql-bugs@lists.postgresql.org,
 PG Bug reporting form <noreply@postgresql.org>
References: <15827-e6ba53a3a7ed543c@postgresql.org>
From: Ireneusz Pluta <ipluta@wp.pl>
Message-ID: <0e778988-67aa-857d-39af-896fa8701e68@wp.pl>
Date: Sat, 1 Jun 2019 21:51:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <15827-e6ba53a3a7ed543c@postgresql.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: pl
X-WP-MailID: 1a25fbb17f3243ac28c64f1cee642146
X-WP-AV: skaner antywirusowy Poczty Wirtualnej Polski
X-WP-SPAM: NO 0000000 [seOl]                               
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

W dniu 2019-05-31 o 17:57, PG Bug reporting form pisze:
> I'm using `pg_services.conf` to provide access to a Postgresql database.

correct name of the services file is "pg_service.conf", not "pg_services.conf" (unless you change it 
with $PGSERVICEFILE).
Are you sure you're touching the right file?