Re: [PERFORM] LIKE Query performance

2009-01-27 Thread Oleg Bartunov
Only wildspeed http://www.sai.msu.su/~megera/wiki/wildspeed has index support for %text% But, it has limitations. Oleg On Tue, 27 Jan 2009, Hari, Balaji wrote: Hi, I am relatively new to PostgreSQL(8.1) and facing the following problem. We have indexes defined on timestamp and description (

[PERFORM] LIKE Query performance

2009-01-27 Thread Hari, Balaji
Hi, I am relatively new to PostgreSQL(8.1) and facing the following problem. We have indexes defined on timestamp and description (create index description_idx on event using btree (description varchar_pattern_ops)) EXPLAIN ANALYZE SELECT event_id, category, current_session_number, description,

Re: [PERFORM] Odd behavior with temp usage logging

2009-01-27 Thread Josh Berkus
Craig Ringer wrote: Josh Berkus wrote: Folks, I turned on temp file logging for PostgreSQL to see if I needed to adjust work_mem. Oddly, it's logging file usage up to 33 times per executed query (and no, the query isn't large enough to need 33 separate sorts). Are you sure there's not a sort

Re: [PERFORM] [PERFORMANCE] Buying hardware

2009-01-27 Thread M. Edward (Ed) Borasky
da...@lang.hm wrote: > that's not quite the opposite of the statement that I was trying to make. > > assuming that you are not running anything else on the system, how much > data can you put on the system and run entirely out of ram. > > the database has it's overhead (sort buffers, indexes, per

Re: [PERFORM] [PERFORMANCE] Buying hardware

2009-01-27 Thread david
On Tue, 27 Jan 2009, M. Edward (Ed) Borasky wrote: da...@lang.hm wrote: On Mon, 26 Jan 2009, David Rees wrote: And yes, the more memory you can squeeze into the machine, the better, though you'll find that after a certain point, price starts going up steeply. Of course, if you only have a 15

Re: [PERFORM] [PERFORMANCE] Buying hardware

2009-01-27 Thread M. Edward (Ed) Borasky
M. Edward (Ed) Borasky wrote: > Given large amounts of RAM and only PostgreSQL running in the server, > the interesting trade-offs become > > a. How little memory can you buy without putting your service level > agreements at risk? > > b. How do you allocate the PostgreSQL-specific memory buffers

Re: [PERFORM] [PERFORMANCE] Buying hardware

2009-01-27 Thread M. Edward (Ed) Borasky
da...@lang.hm wrote: > On Mon, 26 Jan 2009, David Rees wrote: > >> And yes, the more memory you can squeeze into the machine, the better, >> though you'll find that after a certain point, price starts going up >> steeply. Of course, if you only have a 15GB database, once you reach >> 16GB of memo

Re: [PERFORM] [PERFORMANCE] Buying hardware

2009-01-27 Thread A B
>> 4) Use software raid unless you have the money to buy a raid >> controller, in which case here is the ranking of them >> > > Areca and 3ware/Escalade are the two best controllers for the money > out right now. They tend to take turns being the absolute best as > they release new cards. N

Re: [PERFORM] Odd behavior with temp usage logging

2009-01-27 Thread Craig Ringer
Josh Berkus wrote: > Folks, > > I turned on temp file logging for PostgreSQL to see if I needed to > adjust work_mem. Oddly, it's logging file usage up to 33 times per > executed query (and no, the query isn't large enough to need 33 separate > sorts). Are you sure there's not a sort happening i