Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

lionel duboeuf a écrit : Thank you Kevin and Scott for all the explanations. ;-) regards Lionel Sorry for forgetting Jorge also. regards. All this ,encourage me to know more about database management. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make

Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

Thank you Kevin and Scott for all the explanations. ;-) regards Lionel -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

ry problem ? If so, what would you suggest me to do to avoid the problem again ?. Thanks Lionel Kevin Grittner a écrit : lionel duboeuf wrote: Kevin Grittner a écrit : I just reread your original email, and I'm not sure I understand what you meant regarding VACUUM ANAL

Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

ry problem ? If so, what would you suggest me to do to avoid the problem again ?. Thanks Lionel Kevin Grittner a écrit : lionel duboeuf wrote: Kevin Grittner a écrit : I just reread your original email, and I'm not sure I understand what you meant regarding VACUUM ANAL

Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

See as attachment the "correct" query plan for an other 'user'. I confirm by executing manual "VACUUM ANALYZE" that the problem is solved. But what i don't understand is that i would expect autovacuum to do the job. Lionel Kevin Grittner a écrit : lionel d

Re: [PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

Thanks kevin for your answer. Here is some additionnal informations attached as files. regards. Lionel Kevin Grittner a écrit : lionel duboeuf wrote: Some informations: The following problem has been detected on Postgresql 8.3 and 8.4. on System linux or windows Default

[PERFORM] Almost infinite query -> Different Query Plan when changing where clause value

u all, Hope someone would help me understand why only changing a where clause value attribute will have a big impact on query plan and lead to almost unending query. regards lionel This is my query: select element2_.element_seqnum as col_0_0_, element1_.element_seqnum as col_1_0_, l

Re: [PERFORM] Hardware HD choice...

"Scott Marlowe" wrote: > I second this. Partitioning in time in past reporting databases > resulted in huge performance improvements for select queries. Most statements will load data from a single year, but multiple monthes. I have a integer field containing the year and will use it for partit

[PERFORM] Hardware HD choice...

Hello, I have to choose a dedicated server to host a big 8.3 database. The global size of the database (indexes included) will grow by 40 Go every year (40 millions of lines/year) Real data (indexes excluded) will be around 5-7 Go/year. I need to store 4 years of activity. Very few simultaneous u

Re: [PERFORM] Which hardware ?

"Scott Marlowe" wrote: > We had a reporting server with about 80G of data on a machine with 4G > ram last place I worked, and it could take it a few extra seconds to > hit the old data, but the SW RAID-10 on it made it much faster at > reporting than it would have been with a single disk. Would th

Re: [PERFORM] Which hardware ?

"Scott Marlowe" wrote: > You're absolutely right though, we really need to know the value of > fast performance here. the main problem is that my customers are used to have their reporting after few seconds. They want do have 10 times more data but still have the same speed, which is, I think, q

Re: [PERFORM] Which hardware ?

Andrew Sullivan wrote: > You won't need lots of processer, then. can't find less than quad core for this price range... > How big's the database? with 20 millions of rows, the main table is 3.5 Go on win XP. With 8 Go of indexes. I estimate the whole database around 30 Go / year > If you can

[PERFORM] Which hardware ?

Hi, I need to install a 8.3 database and was wondering which hardware would be sufficient to have good performances (less than 30s for² slowest select). Database size: 25 Go /year, 5 years of history One main table containing 40 million lines per year. Batch inserts of 10 lines. Very very fe

Re: [PERFORM] [dspam-users] Postgres vs. MySQL

Casey Allen Shobe wrote the following on 11/27/04 03:11 : I posted about this a couple days ago on dspam-dev... I am using DSpam with PostgreSQL, and like you discovered the horrible performance. The reason is because the default PostgreSQL query planner settings determine that a sequence scan wil