> -----Original Message-----
> From: Magnus Hagander [mailto:mha@sollentuna.net]
> Sent: 19 December 2005 14:50
> To: Dave Page; Martijn van Oosterhout
> Cc: Tom Lane; Christopher Kings-Lynne; Peter Eisentraut;
> pgsql-hackers@postgresql.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.
>
> It makes life easier for us. Only then we can be almost
> certain that all
> apps will ship with 8.0.0, 8.1.0 etc, and nobody will get any minor
> version upgrades.
Why? I'm not advocating that the dll name change with revisions, only
major or minor version changes or if the API changes (which should never
happen from revision to revision (yes, I know...)), depending on which
numbering scheme is used.
Regards, Dave
