Re: [HACKERS] why postgresql is so slow?

2003-09-20 Thread Neil Conway
On Sat, 2003-09-20 at 06:14, Jeff wrote: > Well, that depends. First, turn on stats collecting and run "VACUUM > ANALYZE". That will collect some data about your data which helps the > planner make a good choice. The statistics collector and the statistics collected by ANALYZE have nothing to do w

Re: [HACKERS] why postgresql is so slow?

2003-09-20 Thread Christopher Browne
Jeff <[EMAIL PROTECTED]> wrote: > Then run "VACUUM ANALYZE" every once in a while (depending on how > fast your data changes), like every night for instance. Consider VACUUM and ANALYZE somewhat separately. You need to ANALYZE any time the distribution of the data changes. You need to VACUUM any

Re: [HACKERS] why postgresql is so slow?

2003-09-20 Thread Jeff
Jinqiang Han wrote: > hello, all. > > I have a table about 2 million rows. when I run "select * from table1" in > psql, it will take me about 10 minutes to get the result. I wonder if > postgresql can immediately return result like db2. If you're executing in psql, it's probably trying to load t

Re: [HACKERS] why postgresql is so slow?

2003-09-20 Thread Richard Huxton
On Saturday 20 September 2003 10:38, Jinqiang Han wrote: > hello, all. This isn't really a hackers question - perhaps try the "general","sql" etc lists in future. This list is for questions about the source-code of PG. > I have a table about 2 million rows. when I run "select * from table1" in >

[HACKERS] why postgresql is so slow?

2003-09-20 Thread Jinqiang Han
hello, all. I have a table about 2 million rows. when I run "select * from table1" in psql, it will take me about 10 minutes to get the result. I wonder if postgresql can immediately return result like db2. After that I create a index on a column named id. The time executing "selct * from tab