From: | Justin Clift <justin(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Vince Vielhaber <vev(at)michvhf(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: sequence indexes |
Date: | 2002-01-26 08:08:22 |
Message-ID: | 3C5263F6.1BADDB0B@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> >> I've looked at the problem a little bit --- there's literature more
> >> recent than Lehmann-Yao that talks about how to do btree compaction
> >> without losing concurrency. But it didn't get done for 7.2.
>
> > Yes, there must be. Informix handles this case perfectly.
> > (It uses a background btree cleaner)
As an idle thought, I wonder what other maintenance tasks we could have
a process in the background automatically doing when system activity is
low ?
Maintenance
***********
- Index compaction
- Vacuum of various flavours
Tuning
******
- cpu_tuple costings (and similar) recalculation(s)
Can't think of anything else off the top of my head though.
Regards and best wishes,
Justin Clift
>
> Right, I had hoped to fold it into lazy VACUUM, but ran out of time.
> (Of course, had I known in August that we'd still not have released
> 7.2 by now, I might have kept after it :-()
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Sherry | 2002-01-26 08:09:32 | Re: bug in permission handling? |
Previous Message | Tom Lane | 2002-01-26 06:24:29 | Re: bug in permission handling? |