Re: [PERFORM] A very long running query....

2012-07-21 Thread Ioannis Anagnostopoulos
On 21/07/2012 21:11, Claudio Freire wrote: On Sat, Jul 21, 2012 at 5:10 PM, Claudio Freire wrote: wrote: (feed_all_y2012m07.ship_pos_messages join ais_server.ship_objects on (ship_pos_messages.obj_id = ship_objects.obj_id)) on (message_copies.msg_id = ship_pos_messag

Re: [PERFORM] A very long running query....

2012-07-21 Thread Claudio Freire
On Sat, Jul 21, 2012 at 5:10 PM, Claudio Freire wrote: > wrote: >> (feed_all_y2012m07.ship_pos_messages join >> ais_server.ship_objects on (ship_pos_messages.obj_id = ship_objects.obj_id)) >> on (message_copies.msg_id = ship_pos_messages.msg_id) > > It's this part of the q

Re: [PERFORM] A very long running query....

2012-07-21 Thread Claudio Freire
On Fri, Jul 20, 2012 at 6:19 PM, Ioannis Anagnostopoulos wrote: > (feed_all_y2012m07.ship_pos_messages join > ais_server.ship_objects on (ship_pos_messages.obj_id = ship_objects.obj_id)) > on (message_copies.msg_id = ship_pos_messages.msg_id) It's this part of the query th

Re: [PERFORM] A very long running query....

2012-07-21 Thread Ioannis Anagnostopoulos
On 21/07/2012 20:19, Claudio Freire wrote: On Sat, Jul 21, 2012 at 4:16 PM, Ioannis Anagnostopoulos wrote: I am not sure that I can see an improvement, at least on src_id that have lots of msg_id per day the query never returned even 5 hours later running "exaplain analyze". For smaller src_id

Re: [PERFORM] A very long running query....

2012-07-21 Thread Claudio Freire
On Sat, Jul 21, 2012 at 4:16 PM, Ioannis Anagnostopoulos wrote: > I am not sure that I can see an improvement, at least on src_id that have > lots of msg_id per day the query never returned even 5 hours later running > "exaplain analyze". For smaller src_id > (message wise) there might be some imp

Re: [PERFORM] A very long running query....

2012-07-21 Thread Ioannis Anagnostopoulos
On 21/07/2012 00:10, Tom Lane wrote: Claudio Freire writes: Looking at this: "-> Index Scan using idx_message_copies_wk2_date_src_pos_partial on message_copies_wk2 message_copies (cost=0.00..19057.93 rows=52 width=32) (actual time=62.124..5486270.845 rows=387524 loops=1)"

Re: [PERFORM] A very long running query....

2012-07-21 Thread Ioannis Anagnostopoulos
On 21/07/2012 17:58, Tom Lane wrote: [ Please try to trim quotes when replying. People don't want to re-read the entire thread in every message. ] Ioannis Anagnostopoulos writes: On 21/07/2012 10:16, Marc Mamin wrote: isn't the first test superfluous here ? where extract('day' from mess

Re: [PERFORM] A very long running query....

2012-07-21 Thread Tom Lane
[ Please try to trim quotes when replying. People don't want to re-read the entire thread in every message. ] Ioannis Anagnostopoulos writes: > On 21/07/2012 10:16, Marc Mamin wrote: >> isn't the first test superfluous here ? >> >>> where extract('day' from message_copies.msg_date_rec) = 17 >

Re: [PERFORM] A very long running query....

2012-07-21 Thread Ioannis Anagnostopoulos
On 21/07/2012 10:16, Marc Mamin wrote: RE: [PERFORM] A very long running query Hello, isn't the first test superfluous here ? > where extract('day' from message_copies.msg_date_rec) = 17 > and date_trunc('day', message_copies.msg_date_rec) = '2012-07-17' > Here is the index: >

Re: [PERFORM] A very long running query....

2012-07-21 Thread Marc Mamin
Hello, isn't the first test superfluous here ? > where extract('day' from message_copies.msg_date_rec) = 17 > and date_trunc('day',message_copies.msg_date_rec) = '2012-07-17' > Here is the index: > > CREATE INDEX idx_message_copies_wk2_date_src_pos_partial > ON feed_all_y201

Re: [PERFORM] query overhead

2012-07-21 Thread Craig Ringer
On 07/17/2012 11:33 PM, Andy Halsall wrote: If you're working with ISAM-like access though, cursors may well be very helpful for you. It's a pity for your app that Pg doesn't support cursors that see changes committed after cursor creation, since these are ideal when emulating ISAM "next re

Re: [PERFORM] A very long running query....

2012-07-21 Thread Craig Ringer
On 07/21/2012 06:19 AM, Ioannis Anagnostopoulos wrote: On this Ubuntu installation the default_statistics_target = 1000 and not 100. Do you think that this might be an issue? Nope. You should generally avoid setting default_statistics_target too high anyway; leave it where it is and use ALTER