Eh? Stopping server to do a REINDEX? I use REINDEX all the time and you sure
as hell don't need to stop the server. Unless it's for a system table that
is.
(BTW, 7.0 certainly seems to have had some dodgy index code. 7.2 seems much
better. Fortunatly it only seems to hit multicolumn indexes.)
On Thu, Aug 29, 2002 at 09:26:56PM +1200, Mark Kirkwood wrote:
> Tom Lane wrote:
>
> >It doesn't need a lot of examination in my mind: the cause is surely
> >growth of the index on the toast table.
> >
> >
> You are indeed correct !
>
> A quick check of my test case shows that the toast table growth tails
> off ( provided max_fsm_pages is suitably set), and the unbounded growth
> comes entirely from the toast index.
>
> Applying REINDEX brings the space usage down to a level that compares
> with a non-toasted example.
>
> With respect to the REINDEX workaround - having to re-start your server
> single process for it is a bit fatal if you are 24/7 shop - I think
> altering those high hit tables to have attributes detoasted might be
> better (row length permitting).
>
> Anyway that has *toasted* the need for my currrent little investigation
> (quite enjoyed my romp through the code, so I am not too worried). I
> still have some free time (I am off work after knee operation) so I'm
> now looking for another project....
>
> regards
>
> Mark
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.