![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| ||||
| ||||
|
|
What was wondering is with PSQL would I be able to run the data and the schema backup simultaniously? IIRC psql does NOT have a backup option ... |
|
I would assume that one would fail due to the fact a backup is already being run on that same table? But for the system load AFAIK there is no limit on the backup frequency. |
|
if not would there be much diffrence in the backups being simultaniously as opposed to sequentially? Making multiple backups of single tables may brake referential integraty. |
|
I know there are probably lots of pre-build system to backup postgres avaliable but its a bit of fun and quite interesting learning curve ![]() Do add 'man pg_dump[all]' to your learning curve. |
#3
| |||||
| |||||
|
|
IIRC psql does NOT have a backup option ... sorry me not being clear again, I am using psql to do pg_dump and |
|
But for the system load AFAIK there is no limit on the backup frequency. Be aware of locks that may hold [insert or update] queries thats okay the backup is done when no one is actually using the system |
|
Making multiple backups of single tables may brake referential integraty. Further you may end up NOT backupping the definition of indexes, restrictions and defaults, as well as both the definition and current value of sequences. again me not being very clear I think, I am not making multiple backups |
|
Do add 'man pg_dump[all]' to your learning curve. I am already dynamically writing my pg_dumpall to do the database dump |
|
Just my 2ct Its apprecaited my friend |

#4
| |||
| |||
|
|
I don't know if this is a stupid question to ask or not, but I am currently writing a backup application for Postgres. I am using shell scripts using PSQL to do the actual dumps. IIRC psql does NOT have a backup option ... sorry me not being clear again, I am using psql to do pg_dump and pg_dumpall |
![]() |
| Thread Tools | |
| Display Modes | |
| |