On Fri, Sep 5, 2014 at 9:55 PM, Daniel Browning wrote:
> On Friday 05 September 2014 12:38:26 pm Dave Page wrote:
>> pgAdmin writes that file whenever a user successfully logs into a server
>> with a new password for the first time, and opts to save it.
>
> Ah, that probably explains what happened
On Friday 05 September 2014 12:38:26 pm Dave Page wrote:
> pgAdmin writes that file whenever a user successfully logs into a server
> with a new password for the first time, and opts to save it.
Ah, that probably explains what happened to me. I had all my passwords already
setup in pgpass, and ev
pgAdmin writes that file whenever a user successfully logs into a server with a
new password for the first time, and opts to save it. If the user then edits
the file in notepad (maybe to add new details for a server to use from psql),
they'll run into problems.
--
Dave Page
Blog: http://pgsnak
On Friday 05 September 2014 12:57:21 am Dave Page wrote:
> On Thu, Sep 4, 2014 at 11:23 PM, Daniel Browning wrote:
> > Do you agree with modifying pgAdmin so that it stops converting the EOL
> > characters in the pgpass.conf file from unix-style (\n) to Windows-style
> > (\r\n)?
> >
> > It works f
Hi
On Thu, Sep 4, 2014 at 11:23 PM, Daniel Browning wrote:
> Do you agree with modifying pgAdmin so that it stops converting the EOL
> characters in the pgpass.conf file from unix-style (\n) to Windows-style
> (\r\n)?
>
> It works fine with unix-style line endings, and if the file is in that form
