Re: pg_dump incorrect output in plaintext mode - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump incorrect output in plaintext mode
Date
Msg-id 2978.1346172146@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump incorrect output in plaintext mode  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pg_dump incorrect output in plaintext mode
List pgsql-hackers
Magnus Hagander <magnus@hagander.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Use of systable_beginscan_ordered in event trigger patch
Next
From: Andres Freund
Date:
Subject: Re: Use of systable_beginscan_ordered in event trigger patch