Re: Postgres slower than MS ACCESS - Mailing list pgsql-performance

From Jeff Trout
Subject Re: Postgres slower than MS ACCESS
Date
Msg-id 24B89C42-C597-4571-8BD1-A89073C3C035@torgo.978.org
Whole thread Raw
In response to Re: Postgres slower than MS ACCESS  ("Jay Greenfield" <jag@timberline.ca>)
Responses Re: Postgres slower than MS ACCESS  ("Jay Greenfield" <jag@timberline.ca>)
List pgsql-performance
On Feb 14, 2006, at 3:56 PM, Jay Greenfield wrote:

>> How do you get 4,000+ lines of explain analyze for one update
>> query in a
>> database with only one table?  Something a bit fishy there.
>> Perhaps you
>> mean explain verbose, though I don't really see how that'd be so long
>> either, but it'd be closer.  Could you provide some more sane
>> information?
>
> My mistake - there was 4,000 lines in the EXPLAIN ANALYZE VERBOSE
> output.
> Here is the output of EXPLAIN ANALYZE:
>
> QUERY PLAN
> "Seq Scan on ntdn  (cost=0.00..3471884.39 rows=1221391 width=1592)
> (actual
> time=57292.580..1531300.003 rows=1221391 loops=1)"
> "Total runtime: 4472646.988 ms"
>

Have you been vacuuming or running autovacuum?
If you keep running queries like this you're certianly going to have
a ton of dead tuples, which would def explain these times too.

--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/



pgsql-performance by date:

Previous
From: "Jignesh K. Shah"
Date:
Subject: Re: copy and postgresql.conf
Next
From: "FERREIRA, William (VALTECH)"
Date:
Subject: Re: copy and postgresql.conf