From: Ken Hill <ken@scottshill.com>
To: Bryce Nesbitt <bryce1@obviously.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Non Matching Records in Two Tables
Date: Wed, 15 Feb 2006 07:45:41 -0800
Message-ID: <1140018341.3870.3.camel@localhost.localdomain> (raw)
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>
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.
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-sql@postgresql.org
Cc: ken@scottshill.com, bryce1@obviously.com
Subject: Re: Non Matching Records in Two Tables
In-Reply-To: <1140018341.3870.3.camel@localhost.localdomain>
* 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