Re: pg_dump additional options for performance
От | Joshua D. Drake |
---|---|
Тема | Re: pg_dump additional options for performance |
Дата | |
Msg-id | 20080226104444.4138b2c5@commandprompt.com обсуждение исходный текст |
Ответ на | Re: pg_dump additional options for performance (Jeff Davis <pgsql@j-davis.com>) |
Ответы |
Re: pg_dump additional options for performance
|
Список | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 26 Feb 2008 10:32:59 -0800 Jeff Davis <pgsql@j-davis.com> wrote: > On Tue, 2008-02-26 at 17:16 +0000, Simon Riggs wrote: > > I've not been advocating improving pg_restore, which is where the > > -Fc tricks come in. > > Oh, then it was a miscommunication on my part, because I was talking > about pg_restore, and I assumed you were as well. > IMO the place to start is COPY which is per my tests, slow. Multi worker connection restore is great and I have proven that with some work it can provide o.k. results but it is certainly not acceptable. Let's not fix the middle and ignore the beginning. Sincerely, Joshua D. Drake - -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHxF4fATb/zqfZUUQRAty+AJ0VmYoY1wZ+Sijb/eRiDL+LedKrHgCfZuIn SQTgRqm14gVfubz3u3o54mc= =uIYl -----END PGP SIGNATURE-----
В списке pgsql-hackers по дате отправления: