Re: [HACKERS] Slow count(*) again...

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: david(at)lang(dot)hm
Cc: Віталій Тимчишин <tivv00(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: [HACKERS] Slow count(*) again...
Date: 2011-02-04 07:59:06
Message-ID: 4D4BB1CA.6020400@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

On 02/04/2011 02:32 AM, david(at)lang(dot)hm wrote:
>
> when a copy command is issued, I assume that there is some indication
> of how much data is going to follow.
>
>

No of course there isn't. How would we do that with a stream like STDIN?
Read the code.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Torsten Zühlsdorff 2011-02-04 08:43:23 Re: [HACKERS] Slow count(*) again...
Previous Message Andrew Dunstan 2011-02-04 07:53:55 Re: exposing COPY API

Browse pgsql-performance by date

  From Date Subject
Next Message Віталій Тимчишин 2011-02-04 08:03:39 Talking about optimizer, my long dream
Previous Message Віталій Тимчишин 2011-02-04 07:39:38 Re: [HACKERS] Slow count(*) again...