-
-
-
- Require that each schema (-n / --schema) and table (-t / --table)
- qualifier match at least one schema/table in the database to be dumped.
- Note that if none of the schema/table qualifiers find matches pg_dump
- will generate an error even without --strict-names.
-
- This option has no effect on -N/--exclude-schema, -T/--exclude_table
- or --exclude-table-date. An exclude pattern failing to match
- any objects is not considered an error.
-
-
-
-
+
+
+
+ Require that each schema
+ (/) and table
+ (/) qualifier match at
+ least one schema/table in the database to be dumped. Note that if
+ none of the schema/table qualifiers find
+ matches,
pg_dump will generate an error
+ even without .
+
+ This option has no effect
+ on /,
+ /,
+ or . An exclude pattern failing
+ to match any objects is not considered an error.
+
+
+
+
-
-
-
- Require that each schema (-n / --schema) and table (-t / --table)
- qualifier match at least one schema/table in the backup file.
-
-
-
-
+
+
+
+ Require that each schema
+ (/) and table
+ (/) qualifier match at
+ least one schema/table in the backup file.
+
+
+
+
-
-
-
- When showing progress (option
- (Unix epoch) instead of the number of seconds since the
- beginning of the run. The unit is in seconds, with millisecond
- precision after the dot.
- This helps compare logs generated by various tools.
-
-
-
-
+
+
+
+ When showing progress (option
+ (Unix epoch) instead of the number of seconds since the
+ beginning of the run. The unit is in seconds, with millisecond
+ precision after the dot.
+ This helps compare logs generated by various tools.
+
+
+
+