Bug 960760

Description of problem:
Unable to restore from 3.1 LogCollector DB backup file

backup files created with LogCollector on 3.1 will fail to restore.
This is due to the fact that LogCollector is using PG pg_dump utility with the TAR format in order to backup the database.
Unfortunately, there is a bug (Tom Lane claims that this is a feature,) that in case that TAR format is used the -c flag of pg_dump is not honoured and will create always DROP statements for all database objects in the generated restore.sql script.
(See 
http://www.postgresql.org/message-id/E1TrqX7-0002qd-4e@wrigleys.postgresql.org)

The DROP statements caused DB errors when attempting to restore the backup by 
1) dropping existing DB
2) re creating a new blank db with teh same name
3) using pg_restore to restore database from the backup file

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.create a database backup from LogCollector on 3.1 or use and existing one or use pg_dump with -F t flag to generate this file
2.drop the database using dropdb
3.recreate the database using createdb
4.try to use pg_restore to restore the database from the file in 1)
  
Actual results:
Lots of errors on the DROP statements 

Expected results:

We should be able to restore the database from the LogCollector DB backup file

Additional info:

The only way to resolve that is to create a utility that will 

1) Open the backup TAR file to a directory D
2) Do sed operations on the restore.sql to remove unneeded statements 

After that, the database should be restored with:

psql -U engine -f <D>/restore.sql engine

where <D> is the directory to which the TAR was extracted in 1)