| From: | Steve Wampler <swampler(at)noao(dot)edu> |
|---|---|
| To: | Steve Wampler <swampler(at)noao(dot)edu> |
| Cc: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Postgres-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Help tracking down problem with inserts slowing down... |
| Date: | 2003-12-07 14:52:35 |
| Message-ID: | 20031207145235.GA8734@weaver.tuc.noao.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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 (named 'id_index') in the output of vacuum verbose.
The closest I can find is:
NOTICE: --Relation pg_index--
NOTICE: Pages 2: Changed 0, Empty 0; Tup 56: Vac 0, Keep 0, UnUsed 42.
Total CPU 0.00s/0.00u sec elapsed 0.00 sec.
Which probably isn't correct, right (the name doesn't seem to match)?
The table's entry is:
NOTICE: --Relation attributes_table--
NOTICE: Pages 639: Changed 0, Empty 0; Tup 52846: Vac 0, Keep 0, UnUsed 48.
Total CPU 0.00s/0.01u sec elapsed 0.01 sec.
Thanks!
Steve
--
Steve Wampler -- swampler(at)noao(dot)edu
The gods that smiled on your birth are now laughing out loud.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-12-07 16:52:37 | Re: Help tracking down problem with inserts slowing down... |
| Previous Message | Steve Wampler | 2003-12-07 14:28:16 | Re: Help tracking down problem with inserts slowing down... |