Bug #911: pg_dump/pg_restore fails when using triggers/rules on tables including large objects

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #911: pg_dump/pg_restore fails when using triggers/rules on tables including large objects
Date: 2003-03-17 19:03:48
Message-ID: 20030317190348.5D2824762CF@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Joseph Tate (jtate(at)mi-corporation(dot)com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
pg_dump/pg_restore fails when using triggers/rules on tables including large objects

Long Description
If a table has a large object referenced in a column, but also has a rule/trigger that fires on an update of that column, the trigger/rule will fire when the OIDs are being "fixed up". Triggers and rules should be disabled before fixing OID cross references.

This is where the error occurs
"pg_restore: fixing up large object cross-reference for session_data
pg_restore: fixing large object cross-references for session_data.rendered_ink"
The rule on the session_data table then fires and when it fails, it aborts the restore process, leaving the database in an only partially usable state.

FYI I'm using the 7.2 version of pg_dump and pg_restore. If this has been fixed, I apologize for the mail.

Sample Code

No file was uploaded with this report

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2003-03-17 19:27:19 Bug #912: pg_restore cannot restore individual rule from custom dump
Previous Message Bruce Momjian 2003-03-17 17:59:38 Re: Bug #902: Build problems with 7.3.1 and 7.3.2 on SunOS (crypt.h)