[MIR] postgresql-13

[Christian Ehrhardt ]

postgresql-13 now shows up in hirsute component mismatches.
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html

That is due to postgresql-common being auto-synced and changing the default.

Conceptually this is the same as https://bugs.launchpad.net/ubuntu/+source/postgresql-12/+bug/1851396 and all the others before it.

It seems we can go PG-13 in 21.04 as it looks rather good on the main PG-13 transition. Yet there are still a bunch of blockers left:
https://release.debian.org/transitions/html/postgresql-13.html
I guess those will need 4-6 weeks from now.

But even once those are resolved there will be work for the 2nd and 3rd level indirect dependencies. Like last time postgresql-13-pglogical (already available now) but that has pgl-ddl-deploy that still is missing.
I'd expect another 8 weeks for those.

Then (probably ~January) we will need re-evaluate and make the removal of the postgresql-12 traces part of this request (as we remove the old and promote the new in one go usually).

Due to the above this is documented as MIR so that one looking at mismatches can find it, but not meant to be promoted yet until the to-dos mentioned are resolved.

[Matthias Klose (doko)]

missing bug subscriber, and I don't think we need a MIR for a new version. Please just make sure that only one postgres version ends up in the release

[Christian Ehrhardt  (paelzer)]

Well we had a bug to track things last time, so I thought I create one again.
But ack on everything else (subscriber, removal, ...)

[Christian Ehrhardt  (paelzer)]

Some yet unresolved upstream bugs for dependencies that have to resolve for the transition to complete:
- https://github.com/postgrespro/pg_wait_sampling/issues/26
- https://github.com/Segfault-Inc/Multicorn/issues/261
- https://github.com/enova/pgl_ddl_deploy/issues/55
- https://github.com/citusdata/cstore_fdw/issues/238
- https://github.com/powa-team/powa-archivist/issues/35

[Christian Ehrhardt  (paelzer)]

As Doko already said, this will need no approval - yet I subscribed the mir Team to properly be listed in component mismatches in case someone else comes by we don't want him to loose time searching for this.

[Matthias Klose (doko)]

yes, but the package still needs a bug subscriber

[Christian Ehrhardt  (paelzer)]

On Wed, Nov 11, 2020 at 6:30 PM Matthias Klose <email address hidden>
wrote:

> yes, but the package still needs a bug subscriber
>

Yeah, since we were not yet ready on this it wasn't done yet - thanks for
the ping.
Ubuntu-server is now subscribed.

[Christian Ehrhardt  (paelzer)]

I analyzed test issues.
Merged gvmd to fix one, retriggered a few others (no resolved).

Some further test issues will be fixed in the future, for now there are hints to mitigate them at: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/394114

[Christian Ehrhardt  (paelzer)]

Interim update on the dependent upstream projects I mentioned in commend #3.
This is important if we later need to remove it.
BTW all of them are removed from debian-testing already.

looking good:
- pgl-ddl-deploy fixed in v2.0 (needs debian to merge)
- pg-wait-sampling fixed in 1.1.2 (needs debian to merge)
- powa-archivist will be in 4.1 (yet unreleased by upstream)
yet unclear:
- cstore-fdw mp up but has issues (no more activity on it recently)
- postgresql-multicorn mp up but has issues (no more activity on it recently)

[Christian Ehrhardt  (paelzer)]

postgresql-multicorn is the only one directly holding postgresql-common & postgresql-13 back right now. I filed a request for a test hint at [1].
The obvious alternative (as discussed before) would be removing postgresql-multicorn from hirsute.

[1]: https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/394179

[Christian Ehrhardt  (paelzer)]

FYI postgresql-common 223 and postgresql-13 13.1 are now ready to migrate, but waiting for perl to be ready.

[Christian Ehrhardt  (paelzer)]

Ok, things migrated \o/
As of today I started to clear some remaining dependencies (custom triggers, test fixes, ...) to get rid of postgresql-12 soon.

Right now we are waiting for:
https://github.com/enova/pgl_ddl_deploy/pull/59
Which will unblock pgl-ddl-deploy and due to that also pg-logical.
The tests are good now in local tests, I've added a hint for the time being.
=> https://code.launchpad.net/~paelzer/britney/+git/hints-ubuntu/+merge/394953

Furthermore some leftovers just need removals which is handled in bug 1907110.

[Christian Ehrhardt  (paelzer)]

FYI:
- pgl-ddl-deploy resolved
- postgres-logical + logical-ticker resolved
=> All migrated to -release

The one thing that is left is powa-archivist which has the fix that we discussed and tracked upstream and waits in the new queue.
=> https://ftp-master.debian.org/new/powa-archivist_4.1.0-1.html

[Christian Ehrhardt  (paelzer)]

powa-archivist 4.1 synced and working fine so far.
Just waiting on armhf autopkgtests.
Once that is done we can remove postgresql-12 and thereby complete this.

[Christian Ehrhardt  (paelzer)]

Ok, this is complete.
- PG-13 is migrated and all dependencies with it
- Various leftovers were removed in bug 1907110 and via further NBS removal
- bug 1908185 removed PG-12

This is fully complete.

If cstore-fdw completes and releases support for PG-13 before FeatureFreeze we will happily sync it back (removed atm).
That is tracked in:
https://github.com/citusdata/cstore_fdw/issues/238
https://github.com/citusdata/cstore_fdw/pull/241

Thereby closing this bug as the move to PG-13 is complete in Hirsute.