As another glitch in pg_restore, a combination of options
--single-transaction and --clean raises errors if we restore data
into an empty database. The reason is pg_restore uses DROP <OBJECT>.
The cleanup command fails if the target object doesn't exist.
Is it a TODO item to replace "DROP" into "DROP IF EXISTS"
for cleanup commands in pg_restore?
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
Responses
pgsql-hackers by date
| Next: | From: Fujii Masao | Date: 2010-02-10 05:05:55 |
| Subject: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Previous: | From: Takahiro Itagaki | Date: 2010-02-10 04:24:55 |
| Subject: Re: TRUNCATE+COPY optimization and --jobs=1 in pg_restore |