From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Fast index build vs. PITR |
Date: | 2004-06-01 19:21:25 |
Message-ID: | 4852.1086117685@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> I'm not clear that building from WAL is really going to be that much faster.
> A) algorithmically it's only the factor of log(n) that you're talking about.
> and B) the WAL will have records for every write, not just the final product,
> so it might potentially have a lot more writes to do.
Wrong ... what we log in WAL for a btree index build is just the series
of completed index page images. Recreation of the index would proceed
at whatever your disk read/write bandwidth is.
Like Alvaro, I suspect that people who are using PITR will be concerned
about recovery time, and would not be thrilled with any scenario that
involves REINDEX to get the system back on its feet.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2004-06-01 19:30:08 | Re: Official Freeze Date for 7.5: July 1st, 2004 |
Previous Message | Alvaro Herrera | 2004-06-01 19:17:58 | Re: Fast index build vs. PITR |