Skip site navigation (1) Skip section navigation (2)

Re: pgAdmin corrupts pgpass.conf on windows

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "George Pavlov" <gpavlov(at)mynewplace(dot)com>,<pgadmin-support(at)postgresql(dot)org>
Subject: Re: pgAdmin corrupts pgpass.conf on windows
Date: 2006-05-16 09:46:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-support

> -----Original Message-----
> From: George Pavlov [mailto:gpavlov(at)mynewplace(dot)com] 
> Sent: 16 May 2006 00:51
> To: Dave Page; pgadmin-support(at)postgresql(dot)org
> Subject: RE: [pgadmin-support] pgAdmin corrupts pgpass.conf on windows
> > If you remove your file altogether and just let pgAdmin manage it 
> > itself, does it then corrupt it as well?
> I tried that for a bit a while ago and I did not see any 
> corruption, but I am not sure my tests were exhaustive. The 
> problem is that that is really not a solution for me because 
> I want to be able to have many more server/port/user/password 
> combinations stored in there for psql/script purposes than 
> the few that I need for pgAdmin. For a while I thought that 
> my comment lines (starting with #) were confusing pgAdmin but 
> it seems to do the rearranging with or without comments in 
> there. Another workaround would be to never let pgAdmin store 
> passwords -- that does help although pgAdmin still seems to 
> touch the file (it does not mess it up as bad). If I have to 
> I would take this approach because for my purposes psql 
> scripts/pg_dump/pg_restore are primary to pgAdmin. I was just 
> hoping for a way for the two to coexist peacefully (and also 
> to be able to reuse my Linux .pgpass on Windows).

OK, I think I've found the bug and fixed it - can I mail you an updated
.exe to try?

Regards, Dave.

pgadmin-support by date

Next:From: Hank HsiungDate: 2006-05-17 09:04:56
Subject: autovacuum?
Previous:From: George PavlovDate: 2006-05-15 23:51:12
Subject: Re: pgAdmin corrupts pgpass.conf on windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group