Re: [PERFORM] Help tracking down problem with inserts slowing down...

2003-12-07 Thread Steve Wampler
On Fri, Dec 05, 2003 at 09:54:52PM -0500, Robert Treat wrote: ... A vacuum verbose could give you a good indication if you need to reindex, compare the # of pages in the index with the # in the table. Hmmm, I have a feeling that's not as obvious as I thought... I can't identify the index

Re: [PERFORM] Help tracking down problem with inserts slowing down...

2003-12-07 Thread Tom Lane
Steve Wampler [EMAIL PROTECTED] writes: Hmmm, I have a feeling that's not as obvious as I thought... I can't identify the index (named 'id_index') in the output of vacuum verbose. In 7.2, the index reports look like Index %s: Pages %u; Tuples %.0f. and should appear in the part of the

Re: [PERFORM] Help tracking down problem with inserts slowing

2003-12-07 Thread Steve Wampler
On Fri, 2003-12-05 at 16:38, Neil Conway wrote: (1) Can you confirm that the VACUUM FULL on site B actually removed all the tuples you intended it to remove? Concurrent transactions can limit the amount of data that VACUUM FULL is able to reclaim. If you run

Re: [PERFORM] autovacuum daemon stops doing work after about an hour

2003-12-07 Thread Gaetano Mendola
Gaetano Mendola wrote: Vivek Khera wrote: MTO == Matthew T O'Connor [EMAIL PROTECTED] writes: Then it just sits there. I started it at 11:35am, and it is now 3:30pm. MTO Weird Alphabetically speaking, is vkmlm.public.user_list be the MTO last table in the last schema in the last