| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jorge Gustavo Rocha <jgr(at)geomaster(dot)pt> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15827: Unable to connect on Windows using pg_services.conf using Python psycopg2 |
| Date: | 2019-06-01 18:06:28 |
| Message-ID: | 82724.1559412388@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Jorge Gustavo Rocha <jgr(at)geomaster(dot)pt> writes:
> Hi Tom,
> Thanks for looking at this.
> I've tried with \n and \r\n separators to make sure it wasn't the
> problem. I did a od -c to make sure the endings were the expected ones,
> and I found no difference between just \n or \r\n.
> The psql is able to deal with service=pg_trabalho, so I think libpq is
> reading the file without line end issues.
Yeah, that seems like it puts libpq in the clear, but then where are
things going wrong? I wonder if psycopg2 is not just "passing the
connection parameters down to libpq", but is reading the service
file for itself (and failing to take care about newlines).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-06-01 19:06:27 | Re: inconsistent behaviour of json_to_record and friends with embedded json |
| Previous Message | Fahar Abbas | 2019-06-01 18:02:30 | Re: BUG #15829: PdAdmin 4 gives a Server error trigger/sql/#110003#/properties.sql with VIEWS |