Bug #911: pg_dump/pg_restore fails when using triggers/rules on tables including large objects - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #911: pg_dump/pg_restore fails when using triggers/rules on tables including large objects
Date
Msg-id 20030317190348.5D2824762CF@postgresql.org
Whole thread Raw
List pgsql-bugs
Joseph Tate (jtate@mi-corporation.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
fixingOID 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
anonly 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

pgsql-bugs by date:

Previous
From: Ennio Iannucci
Date:
Subject: strange behaviour of extended ascii characters (LATIN1)
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #912: pg_restore cannot restore individual rule from custom dump