X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 122FC528D7 for ; Fri, 29 Jul 2005 13:21:14 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 79654-08 for ; Fri, 29 Jul 2005 16:21:05 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E66965281A for ; Fri, 29 Jul 2005 13:21:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j6TGL2L3002613; Fri, 29 Jul 2005 12:21:02 -0400 (EDT) To: Steve Lane Cc: pgsql-admin@postgresql.org Subject: Re: Indexes on RAM disk = insanity? In-reply-to: References: Comments: In-reply-to Steve Lane message dated "Fri, 29 Jul 2005 11:32:28 -0400" Date: Fri, 29 Jul 2005 12:21:02 -0400 Message-ID: <2612.1122654062@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200507/251 X-Sequence-Number: 18307 Steve Lane writes: > Or will postgres 8 rebuild an index if it doesn't find it where it expects? No, but there's always REINDEX. > I recognize, or think I do, that PG 8 tablespaces would be required to > accomplish this. It'd certainly make it a lot easier. Also, it's probably not worth the pain to try to move system catalog indexes to RAMdisk --- that'll greatly complicate the restart process. User-table indexes could be fixed just with REINDEX. regards, tom lane