| From: | Sam Barnett-Cormack <s(dot)barnett-cormack(at)lancaster(dot)ac(dot)uk> |
|---|---|
| To: | Vasilis Ventirozos <vendi(at)cosmoline(dot)com> |
| Cc: | Donald Fraser <demolish(at)cwgsy(dot)net>, "" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Are 50 million rows a problem for postgres ? |
| Date: | 2003-09-08 10:42:42 |
| Message-ID: | Pine.LNX.4.50.0309081141280.29054-100000@short.lancs.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, 8 Sep 2003, Vasilis Ventirozos wrote:
> This is a simple statement that i run
>
> core_netfon=# EXPLAIN select spcode,count(*) from callticket group by spcode;
Well, yeah. Whatever you do, a complete seqscan and count is going to
take a long time, in the order of hours rather than days I would expect.
However, you may want to ensure that all tuning in postgresql.conf is
correct, as it may not be using all possible resources. That will
probably only make a small difference.
--
Sam Barnett-Cormack
Software Developer | Student of Physics & Maths
UK Mirror Service (http://www.mirror.ac.uk) | Lancaster University
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2003-09-08 10:54:21 | Re: Are 50 million rows a problem for postgres ? |
| Previous Message | Vasilis Ventirozos | 2003-09-08 10:26:05 | Re: Are 50 million rows a problem for postgres ? |