-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem packing RelStorage #482
Comments
Hi, |
I would prefer not to add a 'force truncate' option, because that would just be hiding the underlying issue, and it's that issue that needs to be fixed (if it isn't database-specific). I've never reproduced anything like this. If you can provide a simple reproducer, that would go a long way to solving this. |
Hi Jason, |
I have the same issue: relstorage-3.5.0, python-3.10, keep_history=no, postgres-9.6, zodbpack fails with "zoid=xyz already exists", running I've tried a bit to reproduce this in isolation (e.g. in a separate psql db on the same server, load some very minimal data into zodb/relstorage with the same application code, run zodbpack, etc), but haven't managed to provoke the error that way. :( |
This is a workaround for zodb/relstorage#482
I am having the same pack issue, both with mysql and postgresql:
I am sharing my 2x configurations and tracebacks below. main config
postgresql 16
mysql 8.0
|
Hi,
As issue #448 was closed, I'm opening a new issue for the same problem...
I'm using RelStorage 3.4.5 with Python 3.5 and PostgreSQL 9.6 on a Debian "Stretch" server, with default settings; the storage (containing 3 millions objects) is history-free, and it is packed each day.
I get the same packing error very frequently; if I truncate the tables, the pack is OK, but the problem appears again a few days after... :-/
Best regards,
Thierry
The text was updated successfully, but these errors were encountered: