Обсуждение: pg_dump verbose start and stop times?

Поиск
Список
Период
Сортировка

pg_dump verbose start and stop times?

От
Ron Johnson
Дата:

"
Specifies verbose mode. This will cause pg_dump to output detailed object comments and start/stop times to the dump file, and progress messages to standard error.
"

But I don't see any timing messages.  What am I misunderstanding in the docs?

$ pg_dump -V
pg_dump (PostgreSQL) 16.9
$ postgres -V
postgres (PostgreSQL) 16.9
$ pg_dump -Fp -v ccoremultid > ~/ccoremultid.sql
pg_dump: last built-in OID is 16383
pg_dump: reading extensions
pg_dump: identifying extension members
pg_dump: reading schemas
pg_dump: reading user-defined tables
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined access methods
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined operator families
pg_dump: reading user-defined text search parsers
pg_dump: reading user-defined text search templates
pg_dump: reading user-defined text search dictionaries
pg_dump: reading user-defined text search configurations
pg_dump: reading user-defined foreign-data wrappers
pg_dump: reading user-defined foreign servers
pg_dump: reading default privileges
pg_dump: reading user-defined collations
pg_dump: reading user-defined conversions
pg_dump: reading type casts
pg_dump: reading transforms
pg_dump: reading table inheritance information
pg_dump: reading event triggers
pg_dump: finding extension tables
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: flagging inherited columns in subtables
pg_dump: reading partitioning data
pg_dump: reading indexes
pg_dump: flagging indexes in partitioned tables
pg_dump: reading extended statistics
pg_dump: reading constraints
pg_dump: reading triggers
pg_dump: reading rewrite rules
pg_dump: reading policies
pg_dump: reading row-level security policies
pg_dump: reading publications
pg_dump: reading publication membership of tables
pg_dump: reading publication membership of schemas
pg_dump: reading subscriptions
pg_dump: reading large objects
pg_dump: reading dependency data
pg_dump: saving encoding = UTF8
pg_dump: saving standard_conforming_strings = on
pg_dump: saving search_path =
pg_dump: creating SCHEMA "dba"
pg_dump: creating EXTENSION "pgstattuple"
pg_dump: creating COMMENT "EXTENSION pgstattuple"
pg_dump: creating FUNCTION "dba.get_fk_referenced_by(text)"
pg_dump: creating FUNCTION "dba.get_fk_references(text)"
pg_dump: creating VIEW "dba.aggregate_cache_hits"
pg_dump: creating VIEW "dba.all_indices"
pg_dump: creating VIEW "dba.all_indices_types"
pg_dump: creating VIEW "dba.latest_vacuum_and_analyze"
pg_dump: creating VIEW "dba.analyze_levels"
pg_dump: creating TABLE "dba.index_bloat_1stg"
pg_dump: creating TABLE "dba.index_bloat_2stg"
pg_dump: creating VIEW "dba.index_cache_hits"
pg_dump: creating VIEW "dba.latest_toast_vacuum"
pg_dump: creating TABLE "dba.pre_analyze_hot"
pg_dump: creating VIEW "dba.statio_tables"
pg_dump: creating TABLE "dba.table_bloat_1stg"
pg_dump: creating TABLE "dba.table_bloat_2stg"
pg_dump: creating VIEW "dba.table_cache_hits"
pg_dump: creating VIEW "dba.toast_cache_hits"
pg_dump: creating TABLE "dba.track_analyze_hot"
pg_dump: creating VIEW "dba.v_parents_and_loners"
pg_dump: creating VIEW "dba.v_relations"
pg_dump: creating VIEW "dba.v_table_size"
pg_dump: processing data for table "dba.index_bloat_1stg"
pg_dump: dumping contents of table "dba.index_bloat_1stg"
pg_dump: processing data for table "dba.index_bloat_2stg"
pg_dump: dumping contents of table "dba.index_bloat_2stg"
pg_dump: processing data for table "dba.pre_analyze_hot"
pg_dump: dumping contents of table "dba.pre_analyze_hot"
pg_dump: processing data for table "dba.table_bloat_1stg"
pg_dump: dumping contents of table "dba.table_bloat_1stg"
pg_dump: processing data for table "dba.table_bloat_2stg"
pg_dump: dumping contents of table "dba.table_bloat_2stg"
pg_dump: processing data for table "dba.track_analyze_hot"
pg_dump: dumping contents of table "dba.track_analyze_hot"
pg_dump: creating CONSTRAINT "dba.index_bloat_1stg index_bloat_1stg_pkey"
pg_dump: creating CONSTRAINT "dba.index_bloat_2stg index_bloat_2stg_pkey"
pg_dump: creating CONSTRAINT "dba.pre_analyze_hot pre_analyze_hot_pkey"
pg_dump: creating CONSTRAINT "dba.table_bloat_1stg table_bloat_1stg_pkey"
pg_dump: creating CONSTRAINT "dba.table_bloat_2stg table_bloat_2stg_pkey"
pg_dump: creating CONSTRAINT "dba.track_analyze_hot track_analyze_hot_pkey"
pg_dump: creating ACL "SCHEMA dba"
pg_dump: creating ACL "dba.TABLE all_indices"
pg_dump: creating ACL "dba.TABLE all_indices_types"
pg_dump: creating ACL "dba.TABLE latest_vacuum_and_analyze"
pg_dump: creating ACL "dba.TABLE analyze_levels"
pg_dump: creating ACL "dba.TABLE latest_toast_vacuum"
pg_dump: creating ACL "dba.TABLE v_relations"

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

Re: pg_dump verbose start and stop times?

От
"David G. Johnston"
Дата:
On Thursday, May 29, 2025, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

"
Specifies verbose mode. This will cause pg_dump to output detailed object comments and start/stop times to the dump file, and progress messages to standard error.
"

But I don't see any timing messages.  What am I misunderstanding in the docs?

It says there the times end up in the dump file, which you redirected and didn’t show the contents of.

David J.

Re: pg_dump verbose start and stop times?

От
Ron Johnson
Дата:
On Thu, May 29, 2025 at 4:42 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thursday, May 29, 2025, Ron Johnson <ronljohnsonjr@gmail.com> wrote:

"
Specifies verbose mode. This will cause pg_dump to output detailed object comments and start/stop times to the dump file, and progress messages to standard error.
"

But I don't see any timing messages.  What am I misunderstanding in the docs?

It says there the times end up in the dump file, which you redirected and didn’t show the contents of.

The non-sense of putting start and stop times in the dump file while not putting them in stderr must have caused my brain to skip over "to the dump file".

Honestly, who cares if start and stop times are in the dump file?  stderr is where a DBA wants to see timings.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

Re: pg_dump verbose start and stop times?

От
Laurenz Albe
Дата:
On Thu, 2025-05-29 at 20:51 -0400, Ron Johnson wrote:
> Honestly, who cares if start and stop times are in the dump file?  stderr is where a DBA wants to see timings.

I guess everybody has different preferences.
These days, few DBAs stare at the screen, waiting for a report on the console
when the job is done.

Yours,
Laurenz Albe