Re: pg_dump incorrect output in plaintext mode

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump incorrect output in plaintext mode
Date: 2012-08-28 16:42:26
Message-ID: 2978.1346172146@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> but in plaintext:
> $ pg_dump -v postgres -Fp -t t > /dev/null
> pg_dump: creating TABLE t
> pg_dump: restoring data for table "t"
> pg_dump: dumping contents of table t
> pg_dump: setting owner and privileges for TABLE t
> pg_dump: setting owner and privileges for TABLE DATA t

I don't see anything particularly incorrect about that. The point of
the --verbose switch is to track what pg_dump is doing, and if what
it's doing involves going through RestoreArchive(), why should we try
to hide the fact?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2012-08-28 16:47:10 Re: Use of systable_beginscan_ordered in event trigger patch
Previous Message Tom Lane 2012-08-28 16:39:50 Use of systable_beginscan_ordered in event trigger patch