#3615 fix different PG capabilities in schema
Merged by tkopecek. Opened by tkopecek.
tkopecek/koji issue3594  into  master

Download 3615.patch

Related: https://pagure.io/koji/issue/3594

I don't love having the schema vary like this, but I guess we have little choice, short of dropping the include altogether (introduced in #3448).

At what point do we think we can require PG>=11?

The change itself looks fine

Are you planning to add a separate PR to address the docs part? I'm a little worried about that getting lost in the shuffle since #3595 is marked as a dup

It is tricky to set up PG11+ requirement here. We can technically live with the older one. RHEL/CentOS 8 has PG10 as default and modules for PG 9.6/10/12/13m while CentOS9 has base 13 and module for 15 now. I would go ahead to PG12 which we're using now.

I would add a docs update here. What do you think? (I'm inclined to say there that we're ok with PG10, but encourages PG12 as better tested).

Metadata Update from @tkopecek:
- Pull-request tagged with: testing-ready

would add a docs update here. What do you think? (I'm inclined to say there that we're ok with PG10, but encourages PG12 as better tested).

Sure, sounds good

Metadata Update from @mfilip:
- Pull-request tagged with: testing-done

rebased onto c11056996b2a6fe5940a4e576d7bcb01a6e40bd9

Commit 369d9292 fixes this pull-request

Pull-Request has been merged by tkopecek

Metadata