| From: | senthilnathan <senthilnathan(dot)t(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Overhead on while doing pg_start_backup |
| Date: | 2011-08-05 05:05:40 |
| Message-ID: | 1312520740225-4668708.post@n5.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
My use case.,
I have a system with master ---> Standby 1
---> Standby 2
replicating to 2 standby servers.
i will use
Incrementally_Updated_Backups(http://wiki.postgresql.org/wiki/Incrementally_Updated_Backups)
for 2 puposes
1. For adding one more standby in the cluster (---> Standby 3)
2. For backup the data.
What will be overhead on master while doing pg_start_backup?
- Sen
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Overhead-on-while-doing-pg-start-backup-tp4668708p4668708.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivekkumar Pandey | 2011-08-05 07:00:36 | postgres table have a large number of relpages and occupied a big memory size |
| Previous Message | Sergey Konoplev | 2011-08-05 03:54:21 | Re: [GENERAL] Odd VACUUM behavior when it is expected to truncate last empty pages |