pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: pierre@desertmoon.com
Cc: daveh@insightdist.com
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Joining bug????
Date: Tue, 27 Oct 1998 21:19:18 -0500 (EST)
Message-ID: <199810280219.VAA05720@candle.pha.pa.us> (raw)
In-Reply-To: <199810280138.BAA10002@out1.ibm.net>

> Thanks David. The vacuum analyze did the trick. I made the invalid 
> assumption that the statistics would be up to date just after a copy and 
> index creation. They were not. As soon as I ran the vacuum across all my 
> tables the explains changed and I got a MAJOR speed increase and the most 
> complicated query takes no more than 4-8 seconds. This is perfect.
> 
> Perhaps this (bug??) should be documented? I've seen documentation 
> relating to the vacuum analyze, but I always made that invalid 
> assumption. *sigh* Ah well you live and you learn. :)

I have beefed up the FAQ:

   For column-specific optimization statistics, use vacuum analyze.
   Vacuum analyze is important for complex multi-join queries, so the
   optimizer can estimate the number of rows returned from each table,
   and choose the proper join order. The backend does not keep track of
   column statistics on its own, and vacuum analyze must be run to
   collect them periodically.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026



view thread (16+ messages)  latest in thread

Message-ID: <199810280219.VAA05720@candle.pha.pa.us>
Permalink:  ../199810280219.VAA05720@candle.pha.pa.us/
Also on:    postgresql.org/message-id/199810280219.VAA05720@candle.pha.pa.us

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: maillist@candle.pha.pa.us, pierre@desertmoon.com, daveh@insightdist.com
  Subject: Re: [SQL] Joining bug????
  In-Reply-To: <199810280219.VAA05720@candle.pha.pa.us>
  References: <199810280138.BAA10002@out1.ibm.net> <199810280219.VAA05720@candle.pha.pa.us>

* 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