Re: Database Select Slow
От | .ep |
---|---|
Тема | Re: Database Select Slow |
Дата | |
Msg-id | 1186750692.099717.150140@m37g2000prh.googlegroups.com обсуждение исходный текст |
Ответ на | Re: Database Select Slow ("A. Kretschmer" <andreas.kretschmer@schollglas.com>) |
Ответы |
Re: Database Select Slow
Re: Database Select Slow |
Список | pgsql-general |
On Aug 10, 9:42 pm, andreas.kretsch...@schollglas.com ("A. Kretschmer") wrote: > am Fri, dem 10.08.2007, um 17:46:11 +0800 mailte carter ck folgendes: > > > Hi all, > > > I am facing a performance issue here. Whenever I do a count(*) on a table > > that contains about 300K records, it takes few minutes to complete. Whereas > > my other application which is counting > 500K records just take less than > > 10 seconds to complete. > > > I have indexed all the essential columns and still it does not improve the > > speed. > > Indexes don't help in this case, a 'select count(*)' forces a seq. scan. > Do you realy need this information? An estimate for the number of rows > can you find in the system catalog (reltuples in pg_class, seehttp://www.postgresql.org/docs/current/interactive/catalog-pg-class.html) Hi, what if I need to do a count with a WHERE condition? E.g., SELECT count(*) from customers where cust_id = 'georgebush' and created_on > current_date - interval '1 week' ; Can I get the info about this from somewhere in the pg system tables as well? Queries like these are very common in most applications, so I'm hoping I can avoid the sequential scans! Many thanks for any tips.
В списке pgsql-general по дате отправления: