Re: [PERFORM] Join optimisation Quandry

2004-01-18 Thread Ceri Storey
-> Seq Scan on title (cost=0.00..190.83 rows=10683 width=26) (actual time=0.143..113.223 rows=10715 loops=17) Total runtime: 10989.661 ms And both client and server are: postgres (PostgreSQL) 7.4.1 Thanks for looking into it. -- Ceri Storey <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [PERFORM] Join optimisation Quandry

2004-01-18 Thread Ceri Storey
the query time by lifting the join of the title out of the RHS of the left outer join into the top-level of the FROM clause; which was really the kind of advice I was after. If this is the wrong list for that kind of thing, please say so. Again, thanks. -- Ceri Storey <[EMAIL PROTECTED]> S

Re: [PERFORM] Join optimisation Quandry

2004-01-18 Thread Ceri Storey
On Sat, Jan 17, 2004 at 01:03:34AM +, Ceri Storey wrote: > Okay, from top to bottom: > > SELECT p1.chan_name, p1.prog_start AS now_start, p1.prog_id, p1.title_text, > p2.prog_start AS next_start, p2.prog_id, p2.title_text, > p1.title_wanted, p2.title_wanted, p1.c

[PERFORM] Join optimisation Quandry

2004-01-16 Thread Ceri Storey
way to optimize the above query? Any clues, or references would be wonderful. Thanks. -- Ceri Storey <[EMAIL PROTECTED]> ---(end of broadcast)--- TIP 8: explain analyze is your friend