From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
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 16:19:30 |
Message-ID: | 1605725206.4401011253722770032.JavaMail.root@sz0030a.emeryville.ca.mail.comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
----- "Joe Kramer" <cckramer(at)gmail(dot)com> wrote:
> On Thu, Sep 24, 2009 at 1:33 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > 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.
> >
>
> Thanks, I found DISABLE TRIGGER commands and deleted them,
> but wish I could find a way to make pg_dump not to add them!
>
You are going to have to use the 8.3 pg_dump :)
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-09-23 16:33:37 | Re: Source for CreatedSharedMemoryAndSemaphores |
Previous Message | Martin Gainty | 2009-09-23 16:12:15 | Source for CreatedSharedMemoryAndSemaphores |