Re: [PERFORM] simple join uses indexes, very slow

2006-03-29 Thread george young
-> Index Scan using parameters_idx on parameters p (cost=0.00..88.72 rows=46 width=22) (actual time=0.023..0.498 rows=164 loops=263) Index Cond: (('team9'::text = p.run) AND ("outer".opset_num = p.opset_num)) Total runtime: 190.821 ms Thank you all very much for yo

Re: [PERFORM] simple join uses indexes, very slow

2006-03-28 Thread george young
On Tue, 28 Mar 2006 19:17:49 +0100 Simon Riggs <[EMAIL PROTECTED]> threw this fish to the penguins: > On Tue, 2006-03-28 at 10:22 -0500, george young wrote: > > > work_mem= 1024 > > Set that higher. > > Try a couple of other plans using enable_* and let us have

Re: [PERFORM] simple join uses indexes, very slow

2006-03-28 Thread george young
On Tue, 28 Mar 2006 09:30:54 +0100 Simon Riggs <[EMAIL PROTECTED]> threw this fish to the penguins: > On Mon, 2006-03-27 at 13:47 -0500, george young wrote: > > > Table sizes: parameters has 2.1512e+07 tuples, run_opsets has 211745 tuples. > > > > explain analy

[PERFORM] simple join uses indexes, very slow

2006-03-27 Thread george young
there something I'm not seeing? [CPU is 950Mhz AMD, 256MB RAM, 15k rpm scsi disk] -- George Young Table sizes: parameters has 2.1512e+07 tuples, run_opsets has 211745 tuples. explain analyze SELECT ro.run, ro.opset_num, p.step_num FROM run_opsets ro, parameters p WHERE ro.run = p.run AND ro

Re: [PERFORM] Observation about db response time

2005-08-30 Thread george young
On Sat, 27 Aug 2005 21:28:57 +0530 (IST) <[EMAIL PROTECTED]> threw this fish to the penguins: > Hello Friends, > We were having a database in pgsql7.4. The database was responding very > slowly even after full vacuum (select > count(*) from some_table_having_18000_records was taking 18 Sec). One

Re: [PERFORM] create index with substr function

2004-10-21 Thread george young
As previously suggested by Stephan Szabo, you need to create a helper function, e.g.: create or replace function after9(text)returns text language plpgsql immutable as ' begin return substr($1, 10); end; '; You may need the "immutable" specification is to allow the function's use in an in

[PERFORM] sourcecode for newly release eRServer?

2003-08-29 Thread george young
I was ecstatic to hear that postgresql.com is releasing the eRServer replication project to postgresql.org as open source! I'm anxious to get my hands on it -- actually I'm desperate: I'm under pressure to produce a warm-failover server for our lab. I REALLY would like to get hands on this code