Re: [GENERAL] Large database

> > > it would be nice if vacuum could figure out if an extent is no longer
> > > in use, and delete it.
> > >
> > > currently, we need to dump the table, then nuke it and restore it.
> >
> > We tried removing the extra extent, but the other backends needed it
> > around because there was no way to tell them that the extra extent file
> > descriptor was useless. You could just stop the postmaster, and delete
> > the zero-length extents, if you really wanted to. Do the extra extent
> > files cause problems for you? If so, we can start to look at some
> > postmaster cleanup of those.
>
> i haven't actually seen the system reduce a numbered extent.
>
> i could be wrong.

You mean it never gets smaller, or never removes it. It currently
doesn't remove it, but vacuum should make then zero size when they are
not needed.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026