The following bug has been logged online:

Bug reference: 1597
Logged by: Jan Behrens
Email address: jan (AT) monso (DOT) de
PostgreSQL version: 8.0.1
Operating system: Linux 2.4.29
Description: pg_dump --verbose ignores --disable-triggers
Details:

pg_dump -a --disable-triggers

gives a different output than

pg_dump -a --disable-triggers -v
or
pg_dump -a --disable-triggers --verbose


When verbose mode is NOT turned on, the output contains:

--
-- Data for Name: address_incoming; Type: TABLE DATA; Schema: mail; Owner:
postgresql
--

-- Disable triggers
UPDATE pg_catalog.pg_class SET reltriggers = 0 WHERE oid =
'address_incoming':g_catalog.regclass;

COPY address_incoming (client, id, address, mailbox, path) FROM stdin;
12 119118 118110 118413
12 119012 118313 118510
[...]


WITH verbose mode, the output looks like this:

--
-- TOC entry 1959 (class 0 OID 98297)
-- Dependencies: 1392
-- Data for Name: address_incoming; Type: TABLE DATA; Schema: mail; Owner:
postgresql
--

COPY address_incoming (client, id, address, mailbox, path) FROM stdin;
12 119118 118110 118413
12 119012 118313 118510
[...]


When verbose mode is turned on, the output for disabling (and enabling) the
triggers is omitted.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

"Jan Behrens" <jan (AT) monso (DOT) de> writes:
Fixed for next release. Thanks for the report.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings