The irony is that I had just disabled pg_autovacuum the previous day during analysis of a wider issue affecting imports of data into the system.

-tfo

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005

On Oct 21, 2004, at 4:05 PM, Dennis Bjorklund wrote:

On Thu, 21 Oct 2004, Thomas F.O'Connell wrote:

  Aggregate  (cost=0.02..0.02 rows=1 width=8) (actual
time=298321.421..298321.422 rows=1 loops=1)
    ->  Nested Loop  (cost=0.00..0.01 rows=1 width=8) (actual
time=1.771..298305.531 rows=2452 loops=1)
          Join Filter: ("inner".id = "outer".id)
          ->  Seq Scan on userdata u  (cost=0.00..0.00 rows=1 width=8)
(actual time=0.026..11.869 rows=2452 loops=1)
          ->  Seq Scan on userdata_history h  (cost=0.00..0.00 rows=1
width=8) (actual time=0.005..70.519 rows=41631 loops=2452)
                Filter: (id = 18181::bigint)

It looks like you have not run ANALYZE recently. Most people run VACUUM ANALYZE every night (or similar) in a cron job.

--
/Dennis Björklund

---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Reply via email to