pgadmin4 icon indicating copy to clipboard operation
pgadmin4 copied to clipboard

Errors in process watcher of restore job: "pg_restore: error: utility failed with exit code: None"

Open LinuxDoku opened this issue 4 months ago • 1 comments

Describe the bug

When restoring a database many of the following errors appear in the job's process watcher, but the database restore finishes successully. When opening the log afterwards the errors are gone.

pg_restore: error: utility failed with exit code: None

It seems to me, the errors are due to "log streaming problems" of pgadmin, and are in no way related to the restore process itself.

While restoring:

Image

After the restore, when job window was closed and reopened at the same location of the log:

Image

To Reproduce

  1. restore a database backup into a newly created database (the restore process needs to take some seconds, so you can open the process watcher before the restore completes)
  2. open the live view of the process log in the process watcher
  3. BUG: between the successful restore operation statements error messages appear which are not in the persistet process log afterwards

Expected behavior

The errors should not appear when live viewing the process watch.

Error message

pg_restore: erstelle INDEX �public.fonts_fontoverride_font_id_ae703c52�
pg_restore: erstelle INDEX �public.fonts_fontoverride_language_id_ccb8c819�
pg_restore: erstelle INDEX �public.lang_language_code_764a7a1d_like�
pg_restore: erstelle INDEX �public.lang_plural_language_id_b5f4646a�
pg_restore: erstelle INDEX �public.memory_from_file�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_md5_index�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_memory_project_id_f26cda43�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_memory_source_language_id_c53ef4ff�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_memory_target_language_id_c44dca3c�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_memory_user_id_1f05b3bb�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.memory_source_trgm�
pg_restore: error: utility failed with exit code: None
pg_restore: erstelle INDEX �public.otp_static_staticdevice_user_id_7f9cff2b�

Desktop (System A):

  • OS: Windows Server 2019
  • pgAdmin version: 9.6
  • Postgres: 16
  • Mode: Desktop
  • Package type: .exe Installer

Desktop (System B):

  • OS: Mac OS 15.6
  • pgAdmin version: 9.5
  • Mode: Desktop
  • Package type: DMG

LinuxDoku avatar Aug 18 '25 09:08 LinuxDoku

Seeing the same when running Analyze from pgAdmin's Maintenance tool and view it using the Process Watcher as it is in progress:

INFO: analyzing "public.jobfieldhistory"
INFO: "jobfieldhistory": scanned 30000 of 335384 pages, containing 949965 live rows and 0 dead rows; 30000 rows in sample, 10620102 estimated total rows
psql: error: utility failed with exit code: None
INFO: analyzing "public.jobfulltext"
INFO: "jobfulltext": scanned 30000 of 38203 pages, containing 261994 live rows and 0 dead rows; 30000 rows in sample, 333632 estimated total rows
psql: error: utility failed with exit code: None

When the job completes and I look at the Process Watcher output for that maintenance run, I don't see the errors listed.

Image

Version: 9.9 Application Mode: Desktop Commit: 91ad54d17bbf82ae0efa277ceb88f30a3189ce4e 2025-10-14 Python Version: 3.13.8 Current User: [email protected] Electron Version: 38.2.2 Browser: Chrome 140.0.7339.133 Operating System: Windows-2016Server-10.0.14393-SP0

garyhampson avatar Nov 01 '25 00:11 garyhampson