Re: [HACKERS] Incrementally Updated Backup
| От | Tom Lane |
|---|---|
| Тема | Re: [HACKERS] Incrementally Updated Backup |
| Дата | |
| Msg-id | 19737.1158789048@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Incrementally Updated Backup ("Jim C. Nasby" <jim@nasby.net>) |
| Ответы |
Re: [HACKERS] Incrementally Updated Backup
|
| Список | pgsql-patches |
"Jim C. Nasby" <jim@nasby.net> writes:
> My thought is that in many envoronments it would take much beefier
> hardware to support N postmasters running simultaneously than to cycle
> through them periodically bringing the backups up-to-date.
How you figure that? The cycling approach will require more total I/O
due to extra page re-reads ... particularly if it's built on a patch
like this one that abandons work-in-progress at arbitrary points.
A postmaster running WAL replay does not require all that much in the
way of CPU resources. It is going to need I/O comparable to the gross
I/O load of its master, but cycling isn't going to reduce that at all.
regards, tom lane
В списке pgsql-patches по дате отправления: