pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeremiah Jahn <jeremiah@cs.earlham.edu>
To: postgres performance <pgsql-performance@postgresql.org>
Subject: Re: cross table indexes or something?
Date: Tue, 02 Dec 2003 13:08:13 -0600
Message-ID: <1070392092.22346.43.camel@bluejay.goodinassociates.com> (raw)
In-Reply-To: <200312011147.51359.josh@agliodbs.com>
References: <1069877651.22346.13.camel@bluejay.goodinassociates.com>
	<1069885949.3176.57.camel@fuji.krosing.net>
	<1070288942.22346.27.camel@bluejay.goodinassociates.com>
	<200312011147.51359.josh@agliodbs.com>

Thanks to all, I had already run analyze.  But the STATISTICS setting
seems to have worked. I'm just not sure what it did..? Would anyone care
to explain. 


On Mon, 2003-12-01 at 13:47, Josh Berkus wrote:
> Jeremiah,
> 
> > I've attached the Analyze below. I have no idea why the db thinks there
> > is only 1 judge named simth. Is there some what I can inform the DB
> > about this. In actuality, there aren't any judges named smith at the
> > moment, but there are 22K people named smith.
> 
> No, Hannu meant that you may need to run the following command:
> 
> ANALYZE actor;
> 
> ... to update the database statistics on the actors table.   That is a 
> maintainence task that needs to be run periodically.
> 
> If that doesn't fix the bad plan, then the granularity of statistics on the 
> full_name column needs updating; I suggest:
> 
> ALTER TABLE actor ALTER COLUMN full_name SET STATISTICS 100;
> ANALYZE actor;
> 
> And if it's still choosing  a slow nested loop, up the stats to 250.
-- 
Jeremiah Jahn <jeremiah@cs.earlham.edu>




view thread (14+ messages)  latest in thread

Message-ID: <1070392092.22346.43.camel@bluejay.goodinassociates.com>
Permalink:  ../1070392092.22346.43.camel@bluejay.goodinassociates.com/
Also on:    postgresql.org/message-id/1070392092.22346.43.camel@bluejay.goodinassociates.com

 · 

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: jeremiah@cs.earlham.edu
  Subject: Re: cross table indexes or something?
  In-Reply-To: <1070392092.22346.43.camel@bluejay.goodinassociates.com>

* 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