Open akorn opened 4 years ago
Ah, that's a built-in table of PostgreSQL, and apparently the proisagg
column got removed in PostgreSQL-11: https://www.postgresql.org/docs/11/release-11.html
Changing the code to use prokind = 'a'
whereever it used proisagg
allows it to continue, but I don't know if this is the correct fix (and obviously it's not universal because this doesn't work with earlier PostgreSQL versions).
This is a real issue which makes Askbot incompatible with PostgreSQL 11.
From the PostgreSQL 11 release notes:
Replace system catalog pg_proc's proisagg and proiswindow columns with prokind (Peter Eisentraut) This new column more clearly distinguishes functions, procedures, aggregates, and window functions.
There is no proisagg
column anymore, but there are some plsql definitions in Askbot that explicitly use it. Consequently each migration which loads such a definition must fail. We need to look at askbot/search/postgresql/*.plsql
.
Besides, the 0.11.x
branch is a (i.e. the only) Python 3 branch of Askbot. If you experience the same issue as described in #735, then you are most likely trying to run the Python 3 branch of Askbot using Python 2.
Hi,
This is with:
My first attempted askbot installation. I pulled the old 1.10.0 version of
six
from the bowels of the Internet to workaround #735. The0.11.x
branch doesn't work for me either; Isetup.py develop
hits a similar error to #735 (I can file a separate issue about it if it makes sense).The
pg_proc
table it created looks like this: