Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [pgadmin-hackers] Client-side password encryption
- From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
- To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
- Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [pgadmin-hackers] Client-side password encryption
- Date: Mon, 19 Dec 2005 13:10:13 +0000
- Message-id: <43A6B135(dot)7060209(at)pse-consulting(dot)de>
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. Regards, Andreas
- Follow-Ups:
- Re: [pgadmin-hackers] Client-side password encryption
- From: Bruce Momjian
- Re: [pgadmin-hackers] Client-side password encryption
- References:
- Re: [pgadmin-hackers] Client-side password encryption
- From: Magnus Hagander
- Re: [pgadmin-hackers] Client-side password encryption
- From: Martijn van Oosterhout
- Re: [pgadmin-hackers] Client-side password encryption
- Prev by Date: Re: [pgadmin-hackers] Client-side password encryption
- Next by Date: Re: [pgadmin-hackers] Client-side password encryption
- Previous by thread: Re: [pgadmin-hackers] Client-side password encryption
- Next by thread: Re: [pgadmin-hackers] Client-side password encryption
- Indexes: