POSTGRESQL 9.51 (using Password) Backup Job stalls



Thank you for the log. Please give us some time to check them.

Sorry for the inconvenience.



Thank you for your log we have checked it. It seems the issue is on pg_dump level. SQLBackupAndFTP creates backups of PostgreSQL Server databases via pg_dump tool.

Could you please try to perform a backup manually via pg_dump tool?

Sorry for the inconvenience.


Thats the thing - while your soft is not working properly, i have to backing up my database throught my script with pg_dump. And it’s work!

@echo Backup database %PG_PATH%%PG_FILENAME%
@echo off
SET 7_BIN=“C:\Program files\7-Zip\7z.exe”
SET PG_BIN=“C:\Program Files\PostgreSQL\10.5-24.1C\bin\pg_dump.exe”
SET PG_HOST=localhost
SET PG_DATABASE1=01_docflow
SET PG_USER=postgres
SET PG_PATH=C:\Program Files\PostgreSQL\10.5-24.1C\bin
SET FECHAYHORA=%date:/=%-%time:-0,8%
Set Tdate=%date:~6,4%%date:~3,2%%date:~0,2%


“C:\Program files\7-Zip\7z.exe” a -tzip -mx8 -r0 C:_Backup%PG_FILENAME1z% C:_Backup%PG_FILENAME1%
“C:\Program files\7-Zip\7z.exe” a -tzip -mx8 -r0 C:_Backup%PG_FILENAME2z% C:_Backup%PG_FILENAME2%
erase /Q C:_Backup%PG_FILENAME1%
erase /Q C:_Backup%PG_FILENAME2%

@echo Backup Taken Complete %PG_PATH%%PG_FILENAME%



Thank you for the details. To investigate this case we need more information. Could you please enable your advanced log with the “Trace” level, reproduce the issue, then open the advanced log

and find the following substring:

SqlBak.Job.PostgreSql.Helper.PgDumpHelper|Dump. Command:

There will be arguments that we pass to pg_dump. Could you please use them and manually try to run those arguments via pg_dump to reproduce the issue.

Sorry for the inconvenience.


I apologize for the delay in responding.
Link to advanced trace log -!Ats40EEpdjy7xx-t7keHyu96lcA9?e=b8hZIy

Target string - “C:\Program Files (x86)\SQLBackupAndFTP\DBMS\PostgreSql\pg_dump.exe”; Arguments: “–host=localhost --port=5432 --username=“postgres” --dbname=“01_docflow” --clean --file=C:\Windows\TEMP\СИСТЕМА\Pranas.NET\SQLBackupAndFTP\backup\01_docflow201908060847.sql --oids --no-privileges --if-exists --lock-wait-timeout=30000”

I was able to do backup successfully with this string. See screenshot in attachement.



Thank you for the details.

We have checked the details you send. Sorry, but the error message you get is generated by pg_dump and cannot be resolved from our side. We recommend you to check this issue on the web, there are many recommendations on how to resolve it.

Sorry for the inconvenience.


Sorry, but there is no error at pg_dump process. Some warnings, but no errors. And process is end successfully - SQL dump generated ok.
But in postgresql this job was freeze\failed.


Thank you for the details.

Yes, indeed, there are no error messages on a screenshot, but SQLbackupAndFTP reports that pg_sump.exe return a non-zero exit code which indicates an error. Could you please run the echo %ERRORLEVEL% command just after you run a backup manually, it will display the exit code pg_dump


Thanks for the answer.
See scrrenshot in attachement.
Exit code is 0.


Thank you for the details. We have added another change to the Alpha edition, could you please install it and check ?

If you still have this issue with the Alpha edition, then please send us the Advanced log with the “Trace” level using the instructions above.

Sorry for the inconvenience.


Still freeze :frowning:
ok, sent. 2223c655-ecfb-4b17-9412-43474384ec07



Thank you for the log, please give us some time to check the issue.

Sorry for the inconvenience.



We have tried to check your logs, but haven’t found them. Could you please send them again?

Sorry for the inconvenience.


Hello, ok sent.
And you can download it here -



Thank you for the details. Please give us some time to check the issue.

Sorry for the delay and for the inconvenience.


Any update?



Sorry for the delay, but we are still working on the issue.

We are really sorry about the delay and all the inconvenience.



Sorry, but we still cannot reproduce the issue and cannot resolve it.

For further investigations and reproducing the issue, could you please export your database without any data and send it to us?

You can export a database manually via pg_dump:

pg_dump --host=<servername> --port=5432 --username="<login>" --dbname="01_docflow" --clean --file=<path_to_dump>.sql --oids --schema-only --no-privileges --if-exists --lock-wait-timeout=30000

Please let us know if you have any further questions.

Sorry for the inconvenience.


ok, you can download it here -

If you want, i can create a test enviroment, reproduce this issue at my server and give you access via TeamViewer. Pls let me now, if it can help.



Thank you for the details. Please give us some time to check the issue.

Thank you for your willingness to provide us with a test environment, we’ll let you know if there will be a need in it.

Sorry for the inconvenience.