Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi to all,
this might be "dumb" question. But we were testing backup script for QSR as documentation says:
.\pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\backup\QSR_backup.tar" QSR
But instead, we executed
.\pg_dump.exe -h localhost -p 4432 -U postgres -v -b -F t -f "D:\BACKUP\QSR_backup.tar"
result:
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 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 publications
pg_dump: reading publication membership
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: saving database definition
pg_dump: dropping DATABASE postgres
pg_dump: creating DATABASE "postgres"
pg_dump: connecting to new database "postgres"
pg_dump: creating COMMENT "DATABASE postgres"
---------
Question what does the other scrip without "QSR" at the end does? We can see at set location backup file but it does not have correct size.
Thank you for any clarification.
Hello ,
You will need to run the full script to capture a full backup.
.\pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\backup\QSR_backup.tar" QSR
According to the documentation:
dbname
Specifies the name of the database to be dumped. If this is not specified, the environment variable PGDATABASE
is used. If that is not set, the user name specified for the connection is used.
Thank you all for support 🙂