| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Subject: | Re: Fast index build vs. PITR |
| Date: | 2004-06-01 02:15:15 |
| Message-ID: | 14278.1086056115@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
>> So AFAICS, we've got to dump the index contents into WAL to support
>> PITR. This is a tad annoying.
> Is it possible in this case to dump the index block by block into the log
> after it has been generated?
That's what we do now, and it more or less doubles the amount of I/O
needed to create an index ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-06-01 02:21:23 | Re: Fast index build vs. PITR |
| Previous Message | Tom Lane | 2004-06-01 02:14:02 | Re: Fast index build vs. PITR |