From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bryce Nesbitt <bryce2@obviously.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
Date: Mon, 30 Nov 2009 22:55:12 -0500
Message-ID: <19189.1259639712@sss.pgh.pa.us> (raw)
In-Reply-To: <4B1491A3.6080602@obviously.com>
References: <4B1491A3.6080602@obviously.com>
Bryce Nesbitt <bryce2@obviously.com> writes:
> I looking at a script that does a pg_restore followed by an immediate
> VACUUM ANALYZE (postgres 8.3).
That's standard.
> Does pg_restore not update the query planner statistics?
Correct. Autovacuum might fix them eventually, but usually it's
worth forcing the issue once you've completed your data loading.
(This might involve multiple steps, which is why pg_restore
doesn't try to force it for you.)
regards, tom lane
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: tgl@sss.pgh.pa.us, bryce2@obviously.com
Subject: Re: pg_restore followed by immediate VACUUM ANALYZE
In-Reply-To: <19189.1259639712@sss.pgh.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