On 5/19/20 7:25 PM, Mark Dadgar wrote:
I get a bunch of these errors because identifiers in postgres are limited to 63 characters and mm3 creates some in sqlite that are longer than that:
2020-05-20T02:16:20.574000Z WARNING PostgreSQL warning: identifier "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6b632_uniq" will be truncated to "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6"
...
etc.
I killed the job before it finished and have not actually tried running against this database, but my question is this:
How does mailman3 handle this limitation with postgres if I set up an instance from scratch using postgres? Does it just truncate the identifiers identically, in which case migrating via pgloader should work?
Mailman doesn't make those names. Those are names in table index entries. Mailman specifies the columns in a table which are indexed, but the DBM itself manages the index.
For reference my pgloader script looks like:
load database from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db into postgresql://mailman3:XXREDACTEDXX@localhost/mailman
with include drop, create tables, create indexes, reset sequences, no truncate
I'm not sure why this doesn't work. A brief look at the pgloader docs seems to say it should.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan