Re: Migration study, step 1: bulk write performance optimization
От | Craig A. James |
---|---|
Тема | Re: Migration study, step 1: bulk write performance optimization |
Дата | |
Msg-id | 441EC652.1010807@modgraph-usa.com обсуждение исходный текст |
Ответ на | Migration study, step 1: bulk write performance optimization ("Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com>) |
Ответы |
update == delete + insert?
Re: Migration study, step 1: bulk write performance optimization |
Список | pgsql-performance |
Mikael Carneholm wrote: > I am responisble for an exciting project of evaluating migration of a > medium/large application for a well-known swedish car&truck manufacturer > ... The goal right now is to find the set of parameters that gives as > short bulk insert time as possible, minimizing downtime while the data > itself is migrated. If you haven't explored the COPY command yet, check it out. It is stunningly fast compared to normal INSERT commands. http://www.postgresql.org/docs/8.1/static/sql-copy.html pg_dump and pg_restore make use of the COPY command. Since you're coming from a different vendor, you'd have to dump thedata into a COPY-compatible set of files yourself. But it will be worth the effort. Craig
В списке pgsql-performance по дате отправления: