pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andy <frum@ar-sd.net>
To: Michael Glaesemann <grzm@myrealbox.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Improving Inner Join Performance
Date: Fri, 6 Jan 2006 11:54:46 +0200
Message-ID: <00b201c612a7$5bca49a0$0b00a8c0@forge> (raw)
References: <001d01c6120b$0d783600$0b00a8c0@forge>
	<20060105132006.19c7cd31.frank@wiles.org>
	<007f01c612a2$94b1a5b0$0b00a8c0@forge>
	<10D92D77-0DC5-4772-98CD-A6799E3A39C8@myrealbox.com>

Sorry, I had to be more specific. 
VACUUM ANALYZE is performed every hour. 

Regards,
Andy.

----- Original Message ----- 
From: "Michael Glaesemann" <grzm@myrealbox.com>
To: "Andy" <frum@ar-sd.net>
Cc: <pgsql-performance@postgresql.org>
Sent: Friday, January 06, 2006 11:45 AM
Subject: Re: [PERFORM] Improving Inner Join Performance


> 
> On Jan 6, 2006, at 18:21 , Andy wrote:
> 
>> Yes I have indexes an all join fields. The tables have around 30  
>> columns each and around 100k rows. The database is vacuumed every  
>> hour.
> 
> Just to chime in, VACUUM != VACUUM ANALYZE. ANALYZE is what updates  
> database statistics and affects query planning. VACUUM alone does not  
> do this.
> 
>>>  Do you have an index on report.id_order ? Try creating an index for
>>>  it if not and run a vacuum analyze on the table to see if it gets
>>>  rid of the sequence scan in the plan.
> 
> Michael Glaesemann
> grzm myrealbox com
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 
>



view thread (10+ messages)  latest in thread

Message-ID: <00b201c612a7$5bca49a0$0b00a8c0@forge>
Permalink:  ../00b201c612a7$5bca49a0$0b00a8c0@forge/
Also on:    postgresql.org/message-id/00b201c612a7$5bca49a0$0b00a8c0@forge

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: frum@ar-sd.net, grzm@myrealbox.com
  Subject: Re: Improving Inner Join Performance
  In-Reply-To: <00b201c612a7$5bca49a0$0b00a8c0@forge>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox