Re: Postgres restore issue - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Postgres restore issue
Date
Msg-id F04C3185-4D74-47B3-A660-AAFB2A730A22@iki.fi
Whole thread Raw
In response to Postgres restore issue  ("Vaidyanathaswamy, Anandsaikrishnan" <avaidyanathaswamy@corelogic.com>)
Responses Re: Postgres restore issue  (Narayanan V <vnarayanan.email@gmail.com>)
List pgsql-hackers
On 25 October 2018 20:27:07 WEST, "Vaidyanathaswamy, Anandsaikrishnan" <avaidyanathaswamy@corelogic.com> wrote:
>We have postgres running in 8.4.22, We have back up from 8.3.7
>When I try to restore, All the tables are not restored, almost 60% of
>the tables not exist, Failed with the following errors.
>
>Any help on this much appreciated.
>
>I am using the below command for pg_restore
>
>nohup pg_restore -c -U postgres  -d gpl_maps
>~/gcs/PostgreSQL/gpl_maps_devgm01.bkup &
>
>
>pg_restore: [archiver (db)] Error from TOC entry 7580; 0 49537695 TABLE
>DATA bldg_footprints gpl-layer-loader
>pg_restore: [archiver (db)] could not execute query: ERROR:  relation
>"bldg_footprints" does not exist
>Command was: COPY bldg_footprints (gid, id, inbld_fid, bld_status,

These errors are coming from restoring the data. Were there any errors before these, from the CREATE TABLE commands?
Youcould try using the -s option, to restore just the schema first, and check if all the tables exist after that. You
couldalso run it without the username and database options, to create a human-readable SQL file. That might give a
betterclue on what's going on. 

- Heikki


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Buildfarm failures for hash indexes: buffer leaks
Next
From: Andres Freund
Date:
Subject: Resetting PGPROC atomics in ProcessInit()