Re: pg_restore - hangs or check on progress

Thanks for this Tom, you're right as

The vendor docs (ESRI) state that I have to pg_restore for public first then do a separate one for the rest of the db

Austen


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: 16 April 2013 15:03
To: Birchall, Austen
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] pg_restore - hangs or check on progress

"Birchall, Austen" <austen.birchall@metoffice.gov.uk> writes:
> The restore completed very quickly but I got the following errors - this is a postgis database
> pg_restore: [archiver (db)] COPY failed for table "admcntry_gl3m0ahcmp__st"
                : ERROR:  ESRI: error getting spatial references for srid = 13: 

> Anybody know what is happening here?

I think pg_restore is not aware that the postgis support tables have to be loaded up before geometric data can be
restored. (That whole area is something that's been greatly improved since 8.4.)  I'd suggest consulting the postgis
docsor mailing lists as to the recommended procedure for dump/restore on older versions. 

            regards, tom lane