[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze
Roger Leigh
rleigh at codelibre.net
Wed Dec 30 12:25:58 UTC 2009
On Wed, Dec 30, 2009 at 10:52:27AM +0100, Dimitri Fontaine wrote:
> That's why I proposed having a single binary package for any extension,
> embedding support for more than one major version of PostgreSQL. That
> would match how the code is maintained.
But is this true universally? Take my postgresql-debversion
extension, for example. In lenny-backports and squeeze, I
supported building against both 8.3 and 8.4 (possibly earlier as
well--untested). For the new version now in unstable, I use
8.4-specific features which means it /won't build/ with 8.3 or
earlier releases.
You still need to know exactly which versions a given release
of a given extension supports--it's not a given that it will
support all versions.
While I think it might be possible to introduce a versionless
extension package name, IMO this should only be a dependency-only
package which installs the extension for the current server version
(like postgresql-client et al).
I have to confess, I'm still not entirely clear what the problem
is here; when you install a new server version, the old extensions
are still available; one just needs to install the equivalent set
for the new server version prior to migrating data. Is the lack
of automation here the problem?
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20091230/5faad990/attachment.pgp>
More information about the Pkg-postgresql-public
mailing list