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

Re: [pgadmin-hackers] Client-side password encryption

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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: 2005-12-19 22:36:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:

>Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
>>Are there any reasons why we shouldn't change the libname with every
>>release like for UNIX? I can't think of any, but you never know...
>Surely that cure is far worse than the disease.  You'd be trading a
>might-break risk (app using new function will fail if used with old
>library) for a guaranteed-to-break risk (*every* app fails if used
>with *any* library version other than what it was built against).
>The Unix version of the idea is considerably more flexible than
>what would happen on Windows.
Different from Unix distros, win32 apps will always bring all their 
required libraries with them, so it's totally under control of the 
developer/packager. There's no such thing as prerequisite packages for 
win32 installs, new lib names will *not* break other apps when installed 
because older ones stay untouched.


In response to

pgsql-hackers by date

Next:From: Michael AdlerDate: 2005-12-19 22:55:51
Subject: free Sun T2000 for PostgreSQL community?
Previous:From: Albert ChinDate: 2005-12-19 21:58:54
Subject: Trouble building 8.1.1 on Tru64 UNIX 5.1

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