| From: | autarch(at)urth(dot)org |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7873: pg_restore --clean tries to drop tables that don't exist |
| Date: | 2013-02-13 20:22:43 |
| Message-ID: | E1U5iqp-0000nA-Uh@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
The following bug has been logged on the website:
Bug reference: 7873
Logged by: Dave Rolsky
Email address: autarch(at)urth(dot)org
PostgreSQL version: 9.2.3
Operating system: Linux
Description:
When you pass the --clean option to pg_restore it tries to drop tables
without checking if they exist. This results in lots of error output. If
you're running pg_restore via an automated process it's very hard to
distinguish between these "ok" errors and real errors.
It should be using "DROP TABLE IF EXISTS" and the equivalent for
constraints.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | joe | 2013-02-14 01:37:04 | BUG #7874: GUC's not in database dumps |
| Previous Message | Tom Lane | 2013-02-13 16:16:59 | Re: Unlisten / listen in a transaction failure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-02-13 20:23:31 | Re: proposal or just idea for psql - show first N rows from relation backslash statement |
| Previous Message | Kevin Grittner | 2013-02-13 20:17:27 | Re: Alias hstore's ? to ~ so that it works with JDBC |