Closed JSmith-Aura closed 2 weeks ago
Looks like when the unique index constraint is added to the potfile table, certain hashes will be too long for the postgres btree.
Possible solutions
Concerns:
hash
field will probably need indexed anywayOn reflection, I think I will use the following solution:
hash
columnCool, I've pushed the above.
Will require the db migration drop index idx_uniq;
(will put in release notes for 0.3.0)
Howdy, after upgrading and running the project (with db migrations) I get this following log line emitted on startup.
Doesnt seem to cause any issues that anyone has mentioned (and I've started a job and it has worked). So not sure if this is something to fix