Tom Lane wrote:
> Christopher Browne <[EMAIL PROTECTED]> writes:
>> A long time ago, in a galaxy far, farpliers [EMAIL PROTECTED] (Patrick
>> Hatcher) wrote:
>>> Answered my own question. I gave up the vacuum full after 150 mins. I
>>> was able to export to a file, vacuum full the empty table, a
Christopher Browne <[EMAIL PROTECTED]> writes:
> A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Patrick Hatcher)
> wrote:
>> Answered my own question. I gave up the vacuum full after 150 mins. I was
>> able to export to a file, vacuum full the empty table, and reimport in less
>>
A long time ago, in a galaxy far, far away, [EMAIL PROTECTED] (Patrick Hatcher) wrote:
> Answered my own question. I gave up the vacuum full after 150 mins. I was
> able to export to a file, vacuum full the empty table, and reimport in less
> than 10 mins. I suspect the empty item pointers and t
Patrick,
> Answered my own question. I gave up the vacuum full after 150 mins. I was
> able to export to a file, vacuum full the empty table, and reimport in less
> than 10 mins. I suspect the empty item pointers and the sheer number of
> removable rows was causing an issue.
Yeah. If you've a
ubject
[PERFORM] vacuum full 100 mins
plus?
07/14/2004 02:29
Should I be concerned that my vacuum process has taken upwards of 100 +
minutes to complete? I dropped all indexes before starting and also
increased the vacuum_mem before starting.
Looking at the output below, it appears that a vacuum full hasn't been done
on this table for quite sometime. W