From: Pham, Thinh <tpham@mail.priority.net>
To: pgsql-sql@postgreSQL.org
Subject: RE: [SQL] Deleting indexes before vacuum?
Date: Sat, 20 Nov 1999 09:29:46 -0600
Message-ID: <551413BBBB03D111BF880060B01AACCE13A013@home.priority.net> (raw)
> -----Original Message-----
> From: Oleg Bartunov [mailto:oleg@sai.msu.su]
> Sent: Saturday, November 20, 1999 1:57 AM
> To: Tom Lane
> Cc: Matthew Hagerty; pgsql-sql@postgreSQL.org
> Subject: Re: [SQL] Deleting indexes before vacuum?
>
>
> I see another reason for index/vacuum/create
> Currently index files grows infinitely because vacuum analyze
> doesn't truncates them. Vadim has implemented in 6.5.3 a
> quick hack for
> index reuse, but indices still grow. This cause a visible performance
> degradation if your table is often updated.
> The question is: what's the right way to do index/vacuum/create ?
> Do I need transaction ?
>
> Regards,
> Oleg
>
Another quick question as we're on this subject: what if i could never shut
the database down to do those drop/vacuum/create steps? I'm asking b/c we're
running a 911 service here and have to be online 24hours/day since you never
know when an emergency call is going to happen. Is there any other way of
keeping the database always online but letting you do preventive maintenance
stuff? How about replication?
Thanks,
Thinh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tpham@mail.priority.net
Subject: Re: [SQL] Deleting indexes before vacuum?
In-Reply-To: <551413BBBB03D111BF880060B01AACCE13A013@home.priority.net>
References: <551413BBBB03D111BF880060B01AACCE13A013@home.priority.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox