listarchiver table missing from postgresql schema

Bug #1343137 reported by John Naggets
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
High
Unassigned

Bug Description

I am currently testing Mailman3 with PostgreSQL and found out that the listarchiver table is missing from the PostgreSQL schema (database/schema/postgres.sql). It is correctly included in SQLite migration schema though (database/schema/sqlite_20130406000000_01.sql).

Due to the missing listarchiver table I get the following exception:

Jul 16 17:56:36 2014 (25554) Uncaught runner exception: relation "listarchiver" does not exist
LINE 1: ...tarchiver.mailing_list_id, listarchiver.name FROM listarchiv...
                                                             ^
Jul 16 17:56:36 2014 (25554) Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/mailman/core/runner.py", line 169, in _one_iteration
    self._process_one_file(msg, msgdata)
  File "/usr/local/lib/python2.7/dist-packages/mailman/core/runner.py", line 252, in _process_one_file
    keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/local/lib/python2.7/dist-packages/mailman/runners/pipeline.py", line 36, in _dispose
    process(mlist, msg, msgdata, pipeline)
  File "/usr/local/lib/python2.7/dist-packages/mailman/core/pipelines.py", line 66, in process
    handler.process(mlist, msg, msgdata)
  File "/usr/local/lib/python2.7/dist-packages/mailman/handlers/rfc_2369.py", line 120, in process
    process(mlist, msg, msgdata)
  File "/usr/local/lib/python2.7/dist-packages/mailman/handlers/rfc_2369.py", line 87, in process
    archiver_set = IListArchiverSet(mlist)
  File "/usr/local/lib/python2.7/dist-packages/zope/component/hookable.py", line 33, in __call__
    return self.__implementation(*args, **kw)
  File "/usr/local/lib/python2.7/dist-packages/zope/component/_api.py", line 156, in adapter_hook
    return sitemanager.queryAdapter(object, interface, name, default)
  File "/usr/local/lib/python2.7/dist-packages/zope/interface/registry.py", line 234, in queryAdapter
    return self.adapters.queryAdapter(object, interface, name, default)
  File "/usr/local/lib/python2.7/dist-packages/mailman/model/mailinglist.py", line 591, in __init__
    ListArchiver.name == archiver_name)).one()
  File "/usr/local/lib/python2.7/dist-packages/storm/store.py", line 1158, in one
    result = self._store._connection.execute(select)
  File "/usr/local/lib/python2.7/dist-packages/storm/databases/postgres.py", line 266, in execute
    return Connection.execute(self, statement, params, noresult)
  File "/usr/local/lib/python2.7/dist-packages/storm/database.py", line 241, in execute
    raw_cursor = self.raw_execute(statement, params)
  File "/usr/local/lib/python2.7/dist-packages/storm/databases/postgres.py", line 276, in raw_execute
    return Connection.raw_execute(self, statement, params)
  File "/usr/local/lib/python2.7/dist-packages/storm/database.py", line 374, in raw_execute
    self._run_execution(raw_cursor, args, params, statement)
  File "/usr/local/lib/python2.7/dist-packages/storm/database.py", line 388, in _run_execution
    self._check_disconnect(raw_cursor.execute, *args)
  File "/usr/local/lib/python2.7/dist-packages/storm/database.py", line 454, in _check_disconnect
    return function(*args, **kwargs)
ProgrammingError: relation "listarchiver" does not exist
LINE 1: ...tarchiver.mailing_list_id, listarchiver.name FROM listarchiv...

Tags: mailman3

Related branches

Barry Warsaw (barry)
tags: added: mailman3
Changed in mailman:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Aurélien Bompard (abompard) wrote :

I've been hit by this bug too, and wrote the following merge request to fix it:
https://code.launchpad.net/~abompard/mailman/pgsql_upgrade/+merge/227289

Revision history for this message
Barry Warsaw (barry) wrote :

I think this issue is no longer valid after the port to SQLAlchemy. Aurelien, I'll let you handle your mp.

Changed in mailman:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.