On 10/24/2012 8:15 PM, Joe Conway wrote:
> On 10/24/2012 04:58 PM, Christopher Browne wrote:
>> Arguably, the failure to restore the triggers isn't a "real" error, if
>> you squint at things in a particular way.
>>
>> Alternatively, I suppose you could do a separate dump of *just* the
>> Slony schema.  That has *some* risk of locking conflict, but it should
>> be an entirely smaller risk, as it's not encompassing the likely-large
>> backup of your application's schema and data.  Dump the Slony schema,
>> and load it first, and that would allow the
>> schema-excluding-Slony-bits to work.
>>
>> But my preference would be to squint at things sideways and say, "It's
>> OK that those triggers didn't load in."
>
> Thanks for the response (and Steve's as well). We are scripting the
> restore and therefore prefer to treat all errors as a failure.
> Unfortunately if we "allow" the restore trigger errors it will make it
> difficult to disallow other errors. But I guess it is something to consider.

Not that this will be of any help for you, but I consider it a missing 
feature of pg_dump that it allows to omit a schema, but not to omit any 
references to that schema like triggers, foreign keys and so on.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin