You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have noticed, both for Postgres and Maria DB, when I had set DEFAULT_PARALLEL_COMPRESSION_THREADS to a wrong value (initially I left it at 'autodetected' and forgot to change), the container did not report any error, but when scheduled backup started, it also completed without errors but all backup files had 0 kb. Once I commented out this variable, all backups have sizezs.
Steps to reproduce
In the compose, set DEFAULT_PARALLEL_COMPRESSION_THREADS to a wrong value, for example:
DEFAULT_PARALLEL_COMPRESSION_THREADS: autodetected
What is the expected correct behavior?
Backups have some sime, not 0 kbs.
Relevant logs and/or screenshots
The logs in console all "normal", as they end with no errors, just complete instantly.
Environment
Docker
Image version / tag: latest
Host OS: Synology DSM NAS OS
Possible fixes
I would guess the container should maybe error out if the variable has not possible value for it to use?
The text was updated successfully, but these errors were encountered:
Summary
Hi, I have noticed, both for Postgres and Maria DB, when I had set DEFAULT_PARALLEL_COMPRESSION_THREADS to a wrong value (initially I left it at 'autodetected' and forgot to change), the container did not report any error, but when scheduled backup started, it also completed without errors but all backup files had 0 kb. Once I commented out this variable, all backups have sizezs.
Steps to reproduce
In the compose, set DEFAULT_PARALLEL_COMPRESSION_THREADS to a wrong value, for example:
DEFAULT_PARALLEL_COMPRESSION_THREADS: autodetected
What is the expected correct behavior?
Backups have some sime, not 0 kbs.
Relevant logs and/or screenshots
The logs in console all "normal", as they end with no errors, just complete instantly.
Environment
Docker
Possible fixes
I would guess the container should maybe error out if the variable has not possible value for it to use?
The text was updated successfully, but these errors were encountered: