X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 401679DCA0F
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 15 Feb 2006 11:45:39 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 48917-02
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 15 Feb 2006 11:45:43 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.192.83])
	by postgresql.org (Postfix) with ESMTP id B03059DC827
	for <pgsql-sql@postgresql.org>; Wed, 15 Feb 2006 11:45:36 -0400 (AST)
Received: from [10.0.1.5] (c-24-20-199-254.hsd1.or.comcast.net[24.20.199.254])
	by comcast.net (rwcrmhc13) with SMTP
	id <20060215154540m1300fkqrqe>; Wed, 15 Feb 2006 15:45:40 +0000
Subject: Re: Non Matching Records in Two Tables
From: Ken Hill <ken@scottshill.com>
Reply-To: ken@scottshill.com
To: Bryce Nesbitt <bryce1@obviously.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <43F26226.1050203@obviously.com>
References: <20060214210829.79695.qmail@web54302.mail.yahoo.com>
	<1139952295.3083.67.camel@localhost.localdomain>
	<43F26226.1050203@obviously.com>
Content-Type: multipart/alternative; boundary="=-MrU0WLvKqU2luFYcKi9H"
Organization: Scotts Hill Associates, Inc.
Date: Wed, 15 Feb 2006 07:45:41 -0800
Message-Id: <1140018341.3870.3.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.1 
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.088 required=5 tests=[AWL=0.087,
 HTML_MESSAGE=0.001]
X-Spam-Score: 0.088
X-Spam-Level: 
X-Archive-Number: 200602/164
X-Sequence-Number: 24174


--=-MrU0WLvKqU2luFYcKi9H
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

On Tue, 2006-02-14 at 15:05 -0800, Bryce Nesbitt wrote:

> Ken Hill wrote:
> >> also (hate to be obvious) have you analyzed lately?
> >>     
> I'd say that's fair game, not obvious.  Vacuum/Analyze is ar so aparent
> to a person moving
> to Postgres from other DB's.
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
> 
>                http://archives.postgresql.org

In my O'Reily "Practical PostgreSQL" book it recommends vacuuming a
production database on a daily basis. I liken this to MS Access'
"compact/repair" procedure.

--=-MrU0WLvKqU2luFYcKi9H
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.8.1">
</HEAD>
<BODY>
On Tue, 2006-02-14 at 15:05 -0800, Bryce Nesbitt wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Ken Hill wrote:</FONT>
<FONT COLOR="#000000">&gt;&gt; also (hate to be obvious) have you analyzed lately?</FONT>
<FONT COLOR="#000000">&gt;&gt;     </FONT>
<FONT COLOR="#000000">I'd say that's fair game, not obvious.  Vacuum/Analyze is ar so aparent</FONT>
<FONT COLOR="#000000">to a person moving</FONT>
<FONT COLOR="#000000">to Postgres from other DB's.</FONT>


<FONT COLOR="#000000">---------------------------(end of broadcast)---------------------------</FONT>
<FONT COLOR="#000000">TIP 4: Have you searched our list archives?</FONT>

<FONT COLOR="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A HREF="http://archives.postgresql.org">http://archives.</FONT>postgresql.org</A>
</PRE>
</BLOCKQUOTE>
In my O'Reily &quot;Practical PostgreSQL&quot; book it recommends vacuuming a production database on a daily basis. I liken this to MS Access' &quot;compact/repair&quot; procedure.
</BODY>
</HTML>

--=-MrU0WLvKqU2luFYcKi9H--