Skip site navigation (1) Skip section navigation (2)

Re: BUG #4860: Indexes gone after restore

From: "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4860: Indexes gone after restore
Date: 2009-06-18 18:07:19
Message-ID: 53F9CF533E1AA14EA1F8C5C08ABC08D204D7F389@ZDND.DND.boston.cob (view raw or flat)
Thread:
Lists: pgsql-bugs
Okay seems to be a sequencing problem. Sorry I should have been paying attention to the screen notices. 

I tried with a simpler db and this is what I get

QUERY:  SELECT proj4text FROM spatial_ref_sys WHERE srid = 4326 LIMIT 1
    Command was: CREATE INDEX assets_building_idx_the_geom_4326 ON building USIN
G gist (public.st_transform(the_geom, 4326));
WARNING: errors ignored on restore: 1

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2612; 1259 27845 INDEX assets_b
uilding_idx_the_geom_4326 postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  relation "spatial_r
ef_sys" does not exist
LINE 1: SELECT proj4text FROM spatial_ref_sys WHERE srid = 4326 LIMI...
                              ^
QUERY:  SELECT proj4text FROM spatial_ref_sys WHERE srid = 4326 LIMIT 1
    Command was: CREATE INDEX assets_building_idx_the_geom_4326 ON building USIN
G gist (public.st_transform(the_geom, 4326));
WARNING: errors ignored on restore: 1;

Any suggestions on how to work around this issue?  I recall even when 
I have this table loaded before I restore, it still doesn't work.  So I think
its still the set schema issue in restore.



-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thu 6/18/2009 1:59 PM
To: Obe, Regina
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #4860: Indexes gone after restore 
 
"Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov> writes:
> Your example seems to work fine for me too.  I'm trying to figure out the best way to give an isolated case without requiring you install a bunch of stuff.

Well, the only two possibilities for an index not being restored are
(1) it's not listed in the dump file, or
(2) the CREATE INDEX command gets an error during the restore.

Which is it, and if (2) what's the error message?

			regards, tom lane



-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-06-18 18:12:58
Subject: Re: unhelpful error message
Previous:From: Tom LaneDate: 2009-06-18 17:59:01
Subject: Re: BUG #4860: Indexes gone after restore

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group