I figured this out, too. But it might be nice to offer, during a reconnect,
to use the saved password (as well as allowing a new one to be typed in).
That would at least avoid people thinking that the save password was lost.
On Thu, Jul 5, 2012 at 1:57 AM, Dave Page wrote:
> That's exactly why
On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails an
That's exactly why it does it.
On Thursday, July 5, 2012, Michael Shapiro wrote:
> I ran into this and the behavior actually make some sense -- PgAdmin can't
> know why the connection was rejected so it has to deal with the possibility
> that the stored might be wrong. One idea is for PgAdmin to
I ran into this and the behavior actually make some sense -- PgAdmin can't
know why the connection was rejected so it has to deal with the possibility
that the stored might be wrong. One idea is for PgAdmin to give an option
of either reconnecting using the stored password or to enter a new one.
On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails an
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
> On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
> > On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
> >> I have taken to making a copy of the password file so that when the
> >> connection fails and PgAdmin removes the password, I ca
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails and PgAdmin removes the password, I can put it back.
I think I've found your issue. Here is the way to
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
> I have taken to making a copy of the password file so that when the
> connection fails and PgAdmin removes the password, I can put it back.
>
I think I've found your issue. Here is the way to trigger it:
1. Start PostgreSQL
2. Start pgA
I have taken to making a copy of the password file so that when the
connection fails and PgAdmin removes the password, I can put it back.
On Wed, Feb 15, 2012 at 4:27 AM, Vik Reykja wrote:
> On Tue, Feb 14, 2012 at 22:45, Guillaume Lelarge
> wrote:
>
>> You can connect without saving the passwo
On Tue, Feb 14, 2012 at 22:45, Guillaume Lelarge wrote:
> You can connect without saving the password: let the "Save password"
> checkbox unchecked.
>
Sure, but then I'd have to enter it in every time. That's not what I
want. I want it to not forget the password just because there was a
connect
On Tue, 2012-02-14 at 22:33 +0100, Vik Reykja wrote:
> On Tue, Feb 14, 2012 at 22:25, Dave Page wrote:
> > 1. connect to server, save password
> > 2. disconnect from server
> > 3. stop server
> > 4. connect to server (fails, of course)
> > 5. start server
>
On Tue, Feb 14, 2012 at 22:25, Dave Page wrote:
> > 1. connect to server, save password
> > 2. disconnect from server
> > 3. stop server
> > 4. connect to server (fails, of course)
> > 5. start server
> > 6. connect to server
> >
> > pgAdmin asks for my password
>
> That's intentional. A failed c
On Tue, 2012-02-14 at 21:25 +, Dave Page wrote:
> On Tue, Feb 14, 2012 at 9:21 PM, Vik Reykja wrote:
> > On Tue, Feb 14, 2012 at 22:03, Guillaume Lelarge
> > wrote:
> >>
> >> On Mon, 2010-11-08 at 16:16 +0100, Guillaume Lelarge wrote:
> >> > Le 06/11/2010 22:35, Guillaume Lelarge a écrit :
>
On Tue, Feb 14, 2012 at 9:21 PM, Vik Reykja wrote:
> On Tue, Feb 14, 2012 at 22:03, Guillaume Lelarge
> wrote:
>>
>> On Mon, 2010-11-08 at 16:16 +0100, Guillaume Lelarge wrote:
>> > Le 06/11/2010 22:35, Guillaume Lelarge a écrit :
>> > > Le 05/11/2010 17:18, Michael Shapiro a écrit :
>> > >> I no
On Tue, Feb 14, 2012 at 22:03, Guillaume Lelarge wrote:
> On Mon, 2010-11-08 at 16:16 +0100, Guillaume Lelarge wrote:
> > Le 06/11/2010 22:35, Guillaume Lelarge a écrit :
> > > Le 05/11/2010 17:18, Michael Shapiro a écrit :
> > >> I noticed that if I have a problem connecting to a server for which
On Mon, 2010-11-08 at 16:16 +0100, Guillaume Lelarge wrote:
> Le 06/11/2010 22:35, Guillaume Lelarge a écrit :
> > Le 05/11/2010 17:18, Michael Shapiro a écrit :
> >> I noticed that if I have a problem connecting to a server for which I have
> >> a
> >> saved password, the entry in pgpass.conf is
Le 06/11/2010 22:35, Guillaume Lelarge a écrit :
> Le 05/11/2010 17:18, Michael Shapiro a écrit :
>> I noticed that if I have a problem connecting to a server for which I have a
>> saved password, the entry in pgpass.conf is deleted.
>> When I later succeed in connecting, the server then prompts fo
Le 05/11/2010 17:18, Michael Shapiro a écrit :
> I noticed that if I have a problem connecting to a server for which I have a
> saved password, the entry in pgpass.conf is deleted.
> When I later succeed in connecting, the server then prompts for a password
> (and the pgpass.conf entry is added bac
I noticed that if I have a problem connecting to a server for which I have a
saved password, the entry in pgpass.conf is deleted.
When I later succeed in connecting, the server then prompts for a password
(and the pgpass.conf entry is added back).
Is it possible to not delete the entry if the conn
19 matches
Mail list logo
