From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Martin Scholes" <marty(at)iicolo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WAL Bypass for indexes |
Date: | 2006-04-05 16:09:07 |
Message-ID: | 7638.1144253347@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Martin Scholes" <marty(at)iicolo(dot)com> writes:
> On a related note, we currently have some indexes that are unsafe during
> recovery (GIST and Hash come to mind).
> In the spirit of making Pg "safe at any speed," would it make sense to put
> some code in the recovery section that rebuilds all indexes whose integrity
> cannot be assured?
This is no longer true for GIST, and hash really ought to be fixed to
support WAL. The combination of a performance advantage and being able
to postpone fixing hash might be enough of a reason to add a
post-recovery index rebuild feature, but I don't think the latter
alone is --- fixing hash would be less work as well as being the "right"
answer.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Scholes | 2006-04-05 16:40:28 | Re: WAL Bypass for indexes |
Previous Message | Jim Nasby | 2006-04-05 15:22:39 | Re: Summer of Code Preparation |