Re: WIP patch for parallel pg_dump
| От | Josh Berkus |
|---|---|
| Тема | Re: WIP patch for parallel pg_dump |
| Дата | |
| Msg-id | 4CFD67C7.1020703@agliodbs.com обсуждение исходный текст |
| Ответ на | Re: WIP patch for parallel pg_dump (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: WIP patch for parallel pg_dump
|
| Список | pgsql-hackers |
> However, if you were doing something like parallel pg_dump you could
> just run the parent and child instances all against the slave, so the
> pg_dump scenario doesn't seem to offer much of a supporting use-case for
> worrying about this. When would you really need to be able to do it?
If you had several standbys, you could distribute the work of the
pg_dump among them. This would be a huge speedup for a large database,
potentially, thanks to parallelization of I/O and network. Imagine
doing a pg_dump of a 300GB database in 10min.
-- -- Josh Berkus PostgreSQL Experts Inc.
http://www.pgexperts.com
В списке pgsql-hackers по дате отправления: