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

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 19 December 2005 15:00
> To: Martijn van Oosterhout
> Cc: Dave Page; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers(at)postgresql(dot)org; Andreas Pflug
> Subject: Re: [HACKERS] [pgadmin-hackers] Client-side password
> encryption
>
> 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).

If it's changed to include the so version, or PG version in the filename
(eg. Libpq41.dll, or libpq82.dll) then all we require is that a vendor
ship the appropriate version with his app. If it installs in a shared
location, it's guaranteed to only be upgraded by a point release because
the windows installers have no convention for including version numbers
in the filenames and will only upgrade a file of the name name, and with
an older version number (from the version resource).

Regards, Dave.