From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Fwd: Tweaking PG (again) |
Date: | 2008-11-13 23:58:31 |
Message-ID: | 20081113235831.GL4062@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Phoenix Kiula escribió:
> >> ----------------------------------------------------------------------------------------------------------------
> >> Index Scan using new_idx_books_userid on books (cost=0.00..493427.14
> >> rows=2 width=31) (actual time=0.428..8400.299 rows=1 loops=1)
> >> Index Cond: ((user_id)::text = 'MYUSER'::text)
> >> Filter: (url_encrypted = 'bed59c2f2d92e306d4481a276bd8a78c4b0532d4'::bpchar)
> >> Total runtime: 8400.349 ms
> >> (4 rows)
> >
> > 8.4 seconds is a very long time to spend looking up a single record.
> > Is this table bloated? What does
> >
> > vacuum verbose books;
> Thanks but this table "books" has autovac on, and it's manually
> vacuumed every hour!
Perhaps try reindexing it. What kind of index is new_idx_books_userid
anyway? btree?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Eric Jain | 2008-11-14 00:24:11 | Granting read-only access to an existing database? |
Previous Message | Dan Armbrust | 2008-11-13 23:08:12 | vacuum output question |