Re: Help! Database restored with disabled triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Kramer <cckramer(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Help! Database restored with disabled triggers
Date: 2009-09-23 15:33:44
Message-ID: 1878.1253720024@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joe Kramer <cckramer(at)gmail(dot)com> writes:
> On Thu, Sep 24, 2009 at 12:53 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> You sure they weren't disabled in the source database?

> Yes, I'm absolutely sure they are not disabled. And in the SQL dump
> file there are no commands that would disable them.

Better take another look for "ALTER TABLE foo DISABLE TRIGGER bar"
commands. Given the information that this is a pre-8.3 pg_dump,
that's exactly the behavior I'd expect, because it's not going to
understand the values it finds in pg_trigger.tgenabled in an 8.3
server.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message AnthonyV 2009-09-23 15:37:24 Re: Advance SQL subquery
Previous Message Merlin Moncure 2009-09-23 15:32:25 Re: Advance SQL subquery