-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
django.db.utils.ProgrammingError: column "proisagg" does not exist #845
Comments
Ah, that's a built-in table of PostgreSQL, and apparently the |
Changing the code to use |
This is a real issue which makes Askbot incompatible with PostgreSQL 11. From the PostgreSQL 11 release notes:
There is no Besides, the |
* ASKBOT#845 * setup_aggregates() used to conditionally DROP AGGREGATE concat_tsvectors(tsvector); - the condition SELECTs a field from an internal table that was removed in Postgresql 11, consequently the function definition, therefore the script, therefore the django migration fails - the problematic code section is a custom implementation of DROP AGGREGATE IF EXISTS - DROP AGGREGATE IF EXSITS has been supported (at least) since Postgres 8.2.23, released 2006 => replaced custom implementation with DROP AGGREGATE IF EXISTS * this patch removes the reference to the changed internal Postgresql table and therefore the issue which makes the script fail using Postgresql 11
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:The text was updated successfully, but these errors were encountered: