Re: pgsql: Remove pg_class.relhaspkey
От | Alvaro Herrera |
---|---|
Тема | Re: pgsql: Remove pg_class.relhaspkey |
Дата | |
Msg-id | 20180315130104.sb7kjshhc4v6a2i5@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: pgsql: Remove pg_class.relhaspkey (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>) |
Ответы |
Re: pgsql: Remove pg_class.relhaspkey
|
Список | pgsql-committers |
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
В списке pgsql-committers по дате отправления: