Re: pg_restore problems and suggested resolution - Mailing list pgsql-hackers

From Joe Conway
Subject Re: pg_restore problems and suggested resolution
Date
Msg-id 402DA9CC.1010700@joeconway.com
Whole thread Raw
In response to Re: pg_restore problems and suggested resolution  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: pg_restore problems and suggested resolution  (Andreas Pflug <pgadmin@pse-consulting.de>)
List pgsql-hackers
Christopher Kings-Lynne wrote:
>> As an implementation issue, I wonder why these things are hacking
>> permanent on-disk data structures anyway, when what is wanted is only a
>> temporary suspension of triggers/rules within a single backend.  Some
>> kind of superuser-only SET variable might be a better idea.  It'd not be
>> hard to implement, and it'd be much safer to use since failures wouldn't
>> leave you with bogus catalog contents.
> 
> I believe oracle and mssql have ALTER TABLE/DISABLE TRIGGER style 
> statements...

Oracle does for sure, but I can tell you that I have seen people bitten 
by triggers inadvertantly left disabled before...I think Tom has a good 
point.

Joe



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: pg_restore problems and suggested resolution
Next
From: Andreas Pflug
Date:
Subject: Re: pg_restore problems and suggested resolution