----- "Joe Kramer" <cckramer@gmail.com> wrote:
> On Thu, Sep 24, 2009 at 1:33 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Joe Kramer <cckramer@gmail.com> writes:
> >> On Thu, Sep 24, 2009 at 12:53 AM, Tom Lane <tgl@sss.pgh.pa.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@comcast.net