Turns out we have a large downtime window pending, so I'm no longer
personally affected by this as I can do my migration the traditional way
(at least until 8.3 - 8.4 migration ;) )
--
Does not build for PostgreSQL 8.2 (or earlier)
https://bugs.launchpad.net/bugs/236749
You received this bug
I changed the bug title. We won't introduce a new package into stables,
nor will we add an -8.2 package to intrepid, since the only supported
PostgreSQL version in 8.04 and intrepid is 8.3.
postgresql-8.2 was removed from Debian unstable and Intrepid, too.
** Summary changed:
- No PostgreSQL
Since we can't upload this to turn it into a proper package, I do not
see much sense to change anything in the source package. You have to
manually build the extension yourself for hardy and intrepid anyway.
If you still use 8.2 for production, I recommend to run Ubuntu 7.10
(Gutsy), where 8.2 is
The use case for this bug is migrating to PG 8.2 from PG 8.3 with little
downtime. This is not possible on either Gutsy or Hardy without manually
building slony1 from source, as slony1 isn't available for PG 8.3 in
Gutsy. Launchpad Production database servers are already running Hardy
however so
Stuart Bishop [2008-06-09 8:50 -]:
The use case for this bug is migrating to PG 8.2 from PG 8.3 with little
downtime. This is not possible on either Gutsy or Hardy without manually
building slony1 from source, as slony1 isn't available for PG 8.3 in
Gutsy.
The idea is that you upgrade
The gutsy package is 1.2.9 which cannot be used with the PG 8.3 package
which is 1.2.13. Similarly, the 1.2.13 tools cannot be used with 1.2.9
version available for PG 8.2. You need to have the same slony version
for both PG 8.2 and PG 8.3 to do the migration.
--
Does not build for PostgreSQL
