From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | david(at)lang(dot)hm, Vitalii Tymchyshyn <tivv00(at)gmail(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 03:13:22 |
Message-ID: | AANLkTi=s7yBPnZEbO6GAk_tUeRH_bZL=fi3NsfKxPKFf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Thu, Feb 3, 2011 at 7:05 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> If you want to randomly pick 10,000 rows out of all the rows that are
> going to be inserted in the table without knowing in advance how many
> there will be, how do you do that?
Maybe you could instead just have it use some % of the rows going by?
Just a guess.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-02-04 03:17:25 | Re: exposing COPY API |
Previous Message | Jeff Davis | 2011-02-04 03:01:10 | Re: [HACKERS] Slow count(*) again... |
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2011-02-04 03:21:21 | Re: getting the most of out multi-core systems for repeated complex SELECT statements |
Previous Message | Jeff Davis | 2011-02-04 03:01:10 | Re: [HACKERS] Slow count(*) again... |