there is no unique or exclusion constraint matching the ON CONFLICT specification about aleph HOT 5 CLOSED

What Aleph version does your new deployment use? What’s the major version of Postgres do you use?

How did you migrate the FtM store database/tables? When looking at the schema of the FtM store tables in the database, there should be a unique index on the id, origin, fragment columns for each table.

from aleph.

What Aleph version does your new deployment use? What’s the major version of Postgres do you use?

Aleph 3.13, same image as previous deployment. Postgres 14, also same as previous deployment.

How did you migrate the FtM store database/tables?

pg_dump and pg_restore, i'll take a look at the indexes, thanks for the pointers.

from aleph.

@monneyboi just wanted to check whether you have zeroed in on a plausible explanation for what happened here. We'd like to try to understand whether this is still a standing issue with the migration process.

from aleph.

@catileptic No, i've got no idea what happened here. We still had the dataset stored somewhere else, so removed the broken set and re-created.

Also, this was not a issue with a aleph migration process, but happened when moving our Aleph between clouds.

from aleph.

@monneyboi I'm closing this, but please feel free to re-open or tag this in a new Issue if you can see this behaviour emerging again

from aleph.