| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| 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:53:47 |
| Message-ID: | 200905290053.n4T0rm325767@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> 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?
Sure, but that assumes you have parallel I/O channels; I assume right
now it is I/O limited.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-05-29 01:00:07 | Re: pg_migrator and an 8.3-compatible tsvector data type |
| Previous Message | Alvaro Herrera | 2009-05-29 00:53:17 | Re: Python 3.0 does not work with PL/Python |