Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
linux:monitoring:zabbix:database:postgresql:partitioning [2020/03/31 14:24] jlucas [Dump the entire Zabbix DB] |
linux:monitoring:zabbix:database:postgresql:partitioning [2020/04/02 08:20] (current) jlucas [Dump individual Zabbix database tables for testing] |
||
|---|---|---|---|
| Line 48: | Line 48: | ||
| pg_dump -U postgres postgres | psql -U zabbix zabbix | pg_dump -U postgres postgres | psql -U zabbix zabbix | ||
| + | |||
| + | ====Dump individual Zabbix database tables for testing==== | ||
| + | |||
| + | The following use of pg_dump and pg_restore performs a data-only backup using the custom-form output option and using INSERTs instead of COPY statements: | ||
| + | pg_dump -U zabbix -a --inserts -t history_str -Fc zabbix | gzip -1 > / | ||
| + | |||
| + | Once the backup is done, drop all data from the table: | ||
| + | psql -U zabbix -c ' | ||
| + | |||
| + | Now restore the data to the table: | ||
| + | gunzip -c zabdb.zabbix.history_str.Pg.gz | pg_restore -U zabbix -d zabbix | ||
