Re: Huge Data
От
Matthew Lunnon
Тема
Re: Huge Data
Дата
Msg-id
003f01c3da9d$46419690$8e8bbd3e@rwanet.co.uk
Список
Дерево обсуждения
Huge Data Sezai YILMAZ <sezai.yilmaz@pro-g.com.tr>
Re: Huge Data Richard Huxton <dev@archonet.com>
Re: Huge Data Sezai YILMAZ <sezai.yilmaz@pro-g.com.tr>
Re: Huge Data Richard Huxton <dev@archonet.com>
Re: Huge Data Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
Re: Huge Data Sezai YILMAZ <sezai.yilmaz@pro-g.com.tr>
Re: Huge Data Franco Bruno Borghesi <franco@akyasociados.com.ar>
Re: Huge Data Shridhar Daithankar <shridhar_daithankar@myrealbox.com>
Re: Huge Data Sezai YILMAZ <sezai.yilmaz@pro-g.com.tr>
Re: Huge Data Richard Huxton <dev@archonet.com>
Re: Huge Data Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Have you run 'vacuum analyze log;'? Also I believe that in Oracle count(1) used to be quicker than count(*).
Matthew
----- Original Message -----From: Sezai YILMAZTo: Richard HuxtonSent: Wednesday, January 14, 2004 12:39 PMSubject: Re: [GENERAL] Huge DataRichard Huxton wrote:
>PG uses MVCC to manage concurrency. A downside of this is that to verify the
>exact number of rows in a table you have to visit them all.
>
>There's plenty on this in the archives, and probably the FAQ too.
>
>What are you using the count() for?
>
>
>
select logid, agentid, logbody from log where logid=3000000;
this query also returns after about 120 seconds. The table log has about
7 million records, and logid is the primary key of log table. What about
that? Why is it too slow?
-sezai
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
_____________________________________________________________________
This e-mail has been scanned for viruses by MCI's Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com
В списке pgsql-general по дате отправления
