| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)enterprisedb(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: pg_migrator and an 8.3-compatible tsvector data type |
| Date: | 2009-05-29 00:26:01 |
| Message-ID: | 20090529002601.GM5156@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > There are so many caveats on pg_migrator (and things that need to be
> > done after the migration is complete) that one starts to wonder if
> > people is not better off just using parallel pg_restore. From Stefan's
> > reported timings I'm not sure that pg_migrator is that much of a benefit
> > in the first place ... unless copy mode can be made much faster. (On
> > link mode it is so much faster that it's worth it, but then you don't
> > have an escape hatch).
>
> That is accurate. I doubt copy mode speed can be improved.
Why not? Right now it's single-threaded. Would it be faster if it ran
several copies in parallel?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-05-29 00:29:40 | Re: PostgreSQL Developer meeting minutes up |
| Previous Message | Kevin Grittner | 2009-05-29 00:12:46 | Re: User-facing aspects of serializable transactions |