Thread: pg*.dll and *.pdb files in psqlODBC have no version numbers
I posted this question to pgsql-general@lists.postgrsql.org last week but on one has responded so posting here now.
We download the ODBC source from http://ftp.postgresql.org and build it on-site, 13.02.0000 in this case.
A colleague noticed that the following files in the psqlODBC MSI for Windows have no version numbers:
pgenlist.dll
pgenlista.dll
pgxalib.dll
pgenlist.pdb
pgenlista.pdb
psqlodbc30a.pdb
psqlodbc35w.pdb
Does anyone know if that is be design or some other reason? Should they have version numbers?
I checked earlier build and the same holds for ODBC 12.02.0000.
Thanks, Mark
Mark Hill <Mark.Hill@sas.com> writes: > I posted this question to pgsql-general@lists.postgrsql.org<mailto:pgsql-general@lists.postgrsql.org> last week but onone has responded so posting here now. > A colleague noticed that the following files in the psqlODBC MSI for Windows have no version numbers: > ... > Does anyone know if that is be design or some other reason? Should they have version numbers? No idea, but actually the pgsql-odbc list would be the most authoritative place for answers, if you find none here. regards, tom lane
On Mon, Oct 02, 2023 at 02:28:58PM +0000, Mark Hill wrote: > A colleague noticed that the following files in the psqlODBC MSI for Windows have no version numbers: > pgenlist.dll > pgenlista.dll > pgxalib.dll > pgenlist.pdb > pgenlista.pdb > psqlodbc30a.pdb > psqlodbc35w.pdb > > Does anyone know if that is be design or some other reason? Should > they have version numbers? Version numbers are critical in MSI installers to make sure that components get updated, so yes, these are important depending on the upgrade mode. (I vaguely remember that there's a hard mode where things are forcibly replaced, and a soft mode where only components with newer version numbers are replaced, but it's from memories from quite a few years ago so I may recall incorrectly). > I checked earlier build and the same holds for ODBC 12.02.0000. Perhaps it would be better to discuss that on the pgsql-odbc list, where the driver is maintained, not pgsql-hackers. -- Michael