From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cvs head : broken regression tests ? |
Date: | 2004-06-09 04:53:53 |
Message-ID: | 16019.1086756833@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> This only applies to dev versions, as the library version is bumped each
> release, I believe.
Bumping the minor version number is part of Bruce's standard per-release
checklist. However, it seems to me that there are some popular
platforms (eg Linux) where a minor version increment isn't really
noticed by the dynamic linker, and only a bump in the major version
number is sufficient to dissuade the linker from seizing on an older
version of the shared library.
Bumping the major version on each release doesn't sound great either,
as it would create binary incompatibility whether we needed it or not.
Anyone see a decent compromise?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-09 05:24:13 | Re: Question regarding dynamic_library_path |
Previous Message | Christopher Kings-Lynne | 2004-06-09 04:03:41 | Re: bug in 7.4 SET WITHOUT OIDs |