Backup not attaching schema prefix to indexes
Posted: Thu 04 Apr 2013 18:05
Hi, (Using VB.Net 2010 & Devart.Data.PostgreSQL 6.6.217.0)
I ran into a problem where by backups are no longer restoring. I've traced the problem to the section in the backup where the indexes are getting created. Here is an example:
CREATE INDEX idx_aiimportlog_contactkey ON aiimportlog USING btree (contactkey NULLS FIRST);
As you can see, the table reference (aiimportlog) has no schema prefix. As a result it's looking in the the Public schema, not finding the table, and erroring out. All other references to the database objects have a schema prefix (schema.tablename, schema.viewname, etc.)
I'd hate to think that all the backups that my customers are making are useless, however, since it appears that the backup file was created incorrectly, I don't see a good way to resolve this.
Any ideas or suggestions would be greatly appreciated.
Sincerely,
Chris Campbell
I ran into a problem where by backups are no longer restoring. I've traced the problem to the section in the backup where the indexes are getting created. Here is an example:
CREATE INDEX idx_aiimportlog_contactkey ON aiimportlog USING btree (contactkey NULLS FIRST);
As you can see, the table reference (aiimportlog) has no schema prefix. As a result it's looking in the the Public schema, not finding the table, and erroring out. All other references to the database objects have a schema prefix (schema.tablename, schema.viewname, etc.)
I'd hate to think that all the backups that my customers are making are useless, however, since it appears that the backup file was created incorrectly, I don't see a good way to resolve this.
Any ideas or suggestions would be greatly appreciated.
Sincerely,
Chris Campbell