Bug in pg_restore or in postmaster itself?

From: Joseph Tate <jtate+pgsql(at)dragonstrider(dot)com>
To: PostgreSQL Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Bug in pg_restore or in postmaster itself?
Date: 2003-12-03 16:44:33
Message-ID: 3FCE12F1.6090203@dragonstrider.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

When using "pg_restore -S postgres -s -vcd DBNAME bkupfile" on an
existing database, I get the following error:

pg_restore: connecting to database for restore
pg_restore: dropping RULE au_d_assigned_template
pg_restore: dropping RULE au_u_assigned_template
... More rules, triggers, constraints, indexes and functions removed
pg_restore: dropping ACL au_assigned_template
pg_restore: dropping TABLE au_assigned_template
pg_restore: NOTICE: rule au_d_assigned_template on table
assigned_template depends on table au_assigned_template
pg_restore: NOTICE: rule au_u_assigned_template on table
assigned_template depends on table au_assigned_template
pg_restore: [archiver (db)] could not execute query: ERROR: Cannot drop
table au_assigned_template because other objects depend on it
Use DROP ... CASCADE to drop the dependent objects too
pg_restore: *** aborted because of error

I find it odd that it refuses to drop table au_assigned_template because
the two rules depend on it when the rules have already been dropped.

If I use the -vCd OTHERDB option and no database exists, it works fine.

I'm using version 7.3.4 on RHEL 3/RHL 9.

Joseph

Browse pgsql-bugs by date

  From Date Subject
Next Message Olaf Hartmann 2003-12-03 16:49:41 libpq3 + ssl memory leak
Previous Message Joseph Tate 2003-12-03 16:42:06 Seg Fault when using modules linked both to libpq and libodbcpsql.