Postgres 14 fails in median migration

Issue #928 resolved
Ed McDonagh created an issue

Possibly to be marked as WontFix (apart from docs) due to issue #789 removing the postgres median migration from the process for version 1.0.

Reported by Anthony Morales on Twitter

At the stage of adding the median database function the following error occurs when using PostgreSQL 14.1 (the current latest version at the time of reporting the issue):

(venv) C:\Users\ed\Documents\OpenREM\install0100\venv\Lib\site-packages\openrem>python manage.py migrate
Operations to perform:
  Synchronize unmigrated apps: solo, django_filters, staticfiles, messages, humanize, django_js_reverse, crispy_forms
  Apply all migrations: remapp, sessions, admin, sites, auth, contenttypes
Synchronizing apps without migrations:
  Creating tables...
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying remapp.0002_0_7_fresh_install_add_median...Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "C:\Users\ed\Documents\OpenREM\install0100\venv\lib\site-packages\django\core\management\__init__.py", line 354, in execute_from_command_line
    utility.execute()
[...]
  File "C:\Users\ed\Documents\OpenREM\install0100\venv\lib\site-packages\django\db\backends\utils.py", line 62, in execute
    return self.cursor.execute(sql)
django.db.utils.ProgrammingError: function array_append(anyarray, anyelement) does not exist

Running the previous major version instead (13.5) works without issue.

Comments (10)

  1. Ed McDonagh reporter

    I saw that (in the release notes), but it seems to be specific to upgrades between postgres versions, so I didn’t look any further.

  2. Ed McDonagh reporter

    But we’re not using this migration in v1.0 are we? So I think we just update the 0.10 docs to stipulate postgres v13 or earlier.

  3. Log in to comment