For our current case I can confirm the following issues being due to this:
- skytools3 (xenial, not in archive later) #1
- pg-repack (bionic/cosmic) #2a
- postgres-plproxy (bionic/cosmic) #2b
The following two seems to be a different error thou:
- postgres-rum
This is more like the Tables were never created with errors like:
"operator does not exist: smallint[] % unknown at character 34"
- pg-partman [i386]
I'm adding bug tasks for those we identified and set them to triaged as we know how to fix them.
#3 - pg-partman [i386] - will stay unhandled until analyzed
#4 - postgres-rum - split this from the others and define is as #4
https:/ /codesearch. debian. net/search? q=%5BSs% 5D%5BEe% 5D%5BTt% 5D%5Cs* client_ min_messages. *fatal
Not sure how I could search that way in a past release, but it gives some confirming hits.
For our current case I can confirm the following issues being due to this:
- skytools3 (xenial, not in archive later) #1
- pg-repack (bionic/cosmic) #2a
- postgres-plproxy (bionic/cosmic) #2b
The following two seems to be a different error thou:
- postgres-rum
This is more like the Tables were never created with errors like:
"operator does not exist: smallint[] % unknown at character 34"
- pg-partman [i386]
I'm adding bug tasks for those we identified and set them to triaged as we know how to fix them.
#3 - pg-partman [i386] - will stay unhandled until analyzed
#4 - postgres-rum - split this from the others and define is as #4