I have a database with some tables for the application settings, lists like users, departments, cities. I want the structure and the data for those tables. So if i get a new user the backup will save it.
But also have some data for historic and calculated data, that data came from another sources and only work for some time and then expire, so backup that data will be a waste. But will need have the structure so the restore will create the tables need it for the application.
right now I'm using this command but this save all table and all data.
pg_dump -U "postgres" -h "local" -p "5432"
-d dbName -F c -b -v -f c:\uti\backup.dmp
I have 2 additional questions regarding pg_dump.
A) docs say option -b is for blob data. I have very big tables, but i guess this options is for only tables with a BLOB field, so shouldn't make any difference in my backup because i don't have those fields ?.
B) I see pg_dump options are for tables and schemas. How you specify if want save the functions code?
backup
... and then another pg_dump to the same file? If that is the case, just submit it as answer so i can vote for it. – Prurigo-b
is for large objects, not forbytea
columns (Postgres' equivalent to aBLOB
isbytea
) – Alcalde--blobs
to include blob objects in dumps. – Workmanlike