I still cannot force pg_dump to disable triggers

> Date: Fri, 16 Mar 2001 22:58:42 +1100
> From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
> To: kovzol(at)math(dot)u-szeged(dot)hu
> Subject: Re: I cannot force pg_dump to disable triggers
>
> At 12:49 16/03/01 +0100, kovacsz wrote:
> >I downloaded the current snapshot and realized that you changed the
> >dumping behaviour about disabling and enabling triggers. Unfortunately I
> >couldn't find the appropriate switches to get the same output before you
> >made this change (I mean beta4). Could you please help? In beta4 I used
> >-xacnDO for the desired result. Now I never get any lines in the output
> >which contains "-- Enable triggers" or "-- Disable triggers".
>
> I just tried:
>
> pg_dump -xacnDO pjw
>
> and got the enable/disable stuff. Can you check that you did a 'make
> distclean' in pg_dump before you ran the dump? The latest rule is that it
> only does an enable/disable if the dump (or restore) is data-only.
Well, I stopped trying it in March but I'm in a need of changing to 7.1 (I
should use Tom's patch). I did a 'make distclean' but no difference: there
are no lines switching the triggers on/off. I'm using "PostgreSQL 7.1 on
i686-pc-linux-gnu, compiled by GCC egcs-2.91.66".

TIA, Zoltan