Re: [pgadmin-hackers] Client-side password encryption - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [pgadmin-hackers] Client-side password encryption
Date
Msg-id 200512211951.jBLJpka03606@candle.pha.pa.us
Whole thread Raw
In response to Re: [pgadmin-hackers] Client-side password encryption  (Andreas Pflug <pgadmin@pse-consulting.de>)
Responses Re: [pgadmin-hackers] Client-side password encryption
Re: [pgadmin-hackers] Client-side password encryption
List pgsql-hackers
Andreas Pflug wrote:
> Martijn van Oosterhout wrote:
> 
> > 
> > So it's only an issue if you have a policy of removing old versions of
> > libpq on upgrades... I'm not sure what's "best practice" on windows in
> > this area.
> 
> When removing the application (in this case: pgsql), you'd remove that 
> old lib as well if it's the only app using it. If you have another 
> application installed, the deinstaller should observe this, and keep the 
> version.
> 
> 
> I'm voting +1 for lib name versions.

If you add a version number to the Win32 libpq name, you have to update
any command-line compile tools that mention libpq after an upgrade.  The
Unix linker knows about version numbers, but the Win32 linker doesn't,
so adding version numbers does add quite a bit of chaos to the Win32
compile world.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Function call with offset and limit
Next
From: Jaime Casanova
Date:
Subject: Re: [pgadmin-hackers] Client-side password encryption