-
Notifications
You must be signed in to change notification settings - Fork 86
pgsql_tmp in PAGE-type backups #246
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
Comments
Hello! What version are you using? Is it backup via ssh? |
Hello! Thank you for reply!
No ssh used. Just backup from main instance to NFS share. |
Hm, looks like a bug to me, I`m going to try to reproduce. |
My command line for PAGE backup was:
Also I've set:
|
I am still running test environment and noticed that pgsql_tmp files exists in every my PAGE-backup. And sizes are different.
|
Hm, that is really strange - I've failed to reproduce the issue. |
Are FULL backups affected too? |
Log attached |
Just FYI: My test environment inserts 10'000 records per 10 minutes using cron job. Do these scrips interesting for you ? |
No, thanks! |
Log of FULL backup |
and YES - full backup has this also. |
That is a regression introduced by 6ed7350. |
Fixed. |
thank you very much! |
It is just a question: doing backup on test installation, I've noticed that one of PAGE backups with ID "QEVARD 2020-08-11 00:43" has abnormal size16GB.
Directory with backup ..../QEVARD/database/base/pgsql_tmp contains large "pgsql_tmp" subdir.
Is it OK, that "pgsql_tmp*" files goes to PAGE backup ?
The text was updated successfully, but these errors were encountered: