![]() According to that answer, the error is harmless, but I would like to remove it from pgAdmin IV output. These errors are not shown on pgAdmin III when I restore using the same database. I would not like to show these error messages, because they seem to be warnings and not errors (PostgreSQL is trying to create a public schema where it already exists). Pg_restore: creating FK CONSTRAINT "public.layer_reference fk_reference_layer_reference1" Pg_restore: warning: errors ignored on restore: 1 Pg_restore: creating FK CONSTRAINT "aces_pilot_area places_pilot_area_fk_street_id" Pg_restore: connecting to database for restore ![]() Pg_restore: creating COMMENT "SCHEMA public" Pg_restore: error: could not execute query: ERROR: schema "public" already exists Pg_restore: from TOC en2200 SCHEMA public postgres ![]() The problem is when I restore the database, pgAdmin IV output shows the following error message: pg_restore: connecting to database for restore The images are: kartoza/postgis:12.0 and dpage/pgadmin4:4.14. I would like to restore this database on my pgAdmin IV with PostgreSQL 12.0 on Docker containers (i.e. I have a database backup from pgAdmin III with PostgreSQL 12.0 (Ubuntu 12.0-2.pgdg16.04+1) on Ubuntu 16.04 LTS.
0 Comments
Leave a Reply. |