From: | Fran Fabrizio <ffabrizio(at)mmrd(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | "'PostgreSQL general list'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: db grows and grows |
Date: | 2002-06-20 13:16:13 |
Message-ID: | 3D11D59D.8030206@mmrd.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Nevermind, I just found it.
http://archives.postgresql.org/pgsql-general/2002-05/msg00242.php
Thanks!
-Fran
>On Wed, Jun 19, 2002 at 06:37:38PM -0400, terry(at)greatgulfhomes(dot)com wrote:
>
>
>>If he needs to REINDEX live without locking out selects, then simply DROP
>>INDEX <indexname>; and then do a CREATE INDEX ... to recreate it. Drop is
>>fast, and the create does not acquire the exclusive lock.
>>
>>The only down side of delete/recreate is that with REINDEX one did not need
>>to know the statement to recreate the index, and the latter does.
>>
>>
>
>A while ago I did post a script that did this, only it did the create first,
>then the drop and then renamed the new index to the old one. All within a
>transaction so other queries wouldn't be left without an index.
>
>It used pg_dump to get the CREATE INDEX command.
>
>Should be in the archive somewhere...
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2002-06-20 13:26:10 | Re: db grows and grows |
Previous Message | Tom Lane | 2002-06-20 13:12:48 | Re: how to evaluate a function only once for a query? |