Andrew Dunstan wrote: > As I mentioned upthread, it's not supposed to be, but was being due to > a typo that I have fixed. You should see this error cleared on the > dashboard in a few minutes. > > However, in general the module tries to do a maximal test. That > includes almost all the contrib databases. That approach has helped > reveal problems several times in the past.
Well, maybe we should dictate policy that it must be possible to pg_upgrade this database too; then we'll just have to work so that it always works. I have fixed the current problem and I'm open to the idea of keeping it working. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
