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

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
Cc: "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>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Subject: Re: [pgadmin-hackers] Client-side password encryption
Date: 2005-12-19 14:12:50
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7EAEE@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> Sent: 19 December 2005 12:07
> To: Martijn van Oosterhout; Dave Page
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers(at)postgresql(dot)org; Andreas Pflug
> Subject: RE: [HACKERS] [pgadmin-hackers] Client-side password
> encryption
>
> Yes.
> If FooApp is compiled against 8.0, it will then be unable to
> run if you
> upgrade libpq to 8.1. IIRC on Unix it will "fall forward" to the new
> version if it's just a minor version upgrade (correct me if
> I'm wrong).
> On windows, it will break with an ugly dialog box. Which is why DLL
> renames are usually only done for backwards incompatible changes.

So each app ships with it's required version of libpq, thus preventing
any issues, including problems caused by finding an older dll with a
different API.

Regards, Dave.

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2005-12-19 14:49:32 Re: [pgadmin-hackers] Client-side password encryption
Previous Message Andrew Sullivan 2005-12-19 13:25:24 Re: Does VACUUM reorder tables on clustered indices