From: mlw <markw@mohawksoft.com>
To: Hannu Krosing <hannu@tm.ee>
Cc: Justin Clift <justin@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Zeugswetter Andreas SB SD <ZeugswetterA@spardat.at>
Cc: Vince Vielhaber <vev@michvhf.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: sequence indexes
Date: Tue, 29 Jan 2002 07:43:52 -0500
Message-ID: <3C569908.2D7254EC@mohawksoft.com> (raw)
References: <46C15C39FEB2C44BA555E356FBCD6FA42128E2@m0114.s-mxs.net>
<6862.1011996346@sss.pgh.pa.us>
<3C5263F6.1BADDB0B@postgresql.org>
<3C55B4E7.29F287B2@mohawksoft.com>
<3C56506C.2AD21A41@tm.ee>
Hannu Krosing wrote:
>
> mlw wrote:
> >
> >
> > Could one run a postgresql process in a lower priority process and
> > perform lazy vacuums without affecting performance all that much?
>
> One must be very careful not to introduce reverse priority problems -
> i.e. a
> lower priority process locking some resource and then not letting go
> while
> higher priority processes are blocked from running due to needing that
> lock.
I understand that, hmm. I wonder if the lock code could boost the priority of a
process which owns a lock.
>
> In my tests 1 vacuum process slowed down 100 concurrent pgbench
> processes
> by ~2 times.
Is that good or bad?
>
> > A live index compaction can be done by indexing the table with a
> > temporary name rename the old index, rename the new index to the old
> > name, and drop the old index.
>
> Isn't this what REINDEX command does ?
REINDEX can't be run on a live system, can it?
>
> ---------------
> Hannu
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: markw@mohawksoft.com, hannu@tm.ee, justin@postgresql.org, tgl@sss.pgh.pa.us, ZeugswetterA@spardat.at, vev@michvhf.com
Subject: Re: sequence indexes
In-Reply-To: <3C569908.2D7254EC@mohawksoft.com>
* 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