Re: pg_dump additional options for performance
От | Jochem van Dieten |
---|---|
Тема | Re: pg_dump additional options for performance |
Дата | |
Msg-id | f96a9b830802240522u2dbf4cdci51b2bfc58ecabd25@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_dump additional options for performance (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_dump additional options for performance
Re: pg_dump additional options for performance |
Список | pgsql-hackers |
On Mon, Feb 11, 2008 at 5:51 PM, Tom Lane wrote: > I agree. Since any multiple-output-file case can't usefully use stdout, > I think we should combine the switches and just have one switch that > says both that you want separated output and what the target filename > is. Thus something like > > --pre-schema-file = foo > --data-file = bar > --post-schema-file = baz Or we could have a switch that specifies a directory and have pg_dump split the dump not just in pre-schema, data and post-schema, but also split the data in a file for each table. That would greatly facilitate a parallel restore of the data through multiple connections. Jochem
В списке pgsql-hackers по дате отправления: