Re: query performance, though it was timestamps,maybe just table size?

From: Henry Drexler <alonup8tb(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: query performance, though it was timestamps,maybe just table size?
Date: 2012-11-30 20:22:45
Message-ID: CAAtgU9Q40odKm+xAZNag_nc1bjZ9XBPNNsA3J+wgjpVQ8FrNGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Nov 30, 2012 at 1:42 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> Can you report the EXPLAIN (ANALYZE, BUFFERS) instead?

Thanks, here they are:

for the approx 65 million row approx 50 min version:

EXPLAIN (ANALYZE, BUFFERS)
select
massive_expansion(ctn,the_range)
from
critical_visitors;

"Seq Scan on critical_visitors (cost=0.00..168722.28 rows=628778 width=40)
(actual time=0.655..3003921.066 rows=628778 loops=1)"
" Buffers: shared hit=4513040 read=1591722 dirtied=5234 written=10"
"Total runtime: 3004478.053 ms"

for the approx 30 million row approx 4 min version:

EXPLAIN (ANALYZE, BUFFERS)
select
massive_expansion(ctn,the_range)
from
critical_visitors;

"Seq Scan on critical_visitors (cost=0.00..746587.90 rows=2782315
width=40) (actual time=393.001..277108.379 rows=2782315 loops=1)"
" Buffers: shared hit=26370078 read=400301 dirtied=33772 written=1030"
"Total runtime: 278988.544 ms"

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Henry Drexler 2012-11-30 20:24:03 Re: query performance, though it was timestamps,maybe just table size?
Previous Message Igor Neyman 2012-11-30 19:33:17 Re: pg_listening_channels()