On Dec 15, 2004, at 10:02 AM, Scott Marlowe wrote:
On Tue, 2004-12-14 at 18:43, Dann Corbit wrote:Would it be possible to rebuild all non-btree indexes when a recovery takes place?
Considering how long I've seen some large hash indexes take to build, that might be better left as an optional setting.
Another thing that seems it might be nice is to check the non-btree indexes during analyze (if that is possible and not too expensive).
-----Original Message----- From: Neil Conway [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 14, 2004 4:39 PM To: Scott Marlowe Cc: Dann Corbit; pgsql-general Subject: Re: [GENERAL] Corrupt RTREE index
On Tue, 2004-12-14 at 14:12 -0600, Scott Marlowe wrote:IS this same issue true for hash or GiST indexes?
Yes, it is: currently, only btree indexes are WAL safe.
(I spent some time recently looking into adding page-level concurrency
and WAL to GiST, but I haven't had a chance to finish that work -- it is
quite a big job...)
-Neil
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
----------------------------------------------------------- Frank D. Engel, Jr. <[EMAIL PROTECTED]>
$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life.
$
___________________________________________________________ $0 Web Hosting with up to 120MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
