Re: pg_dump ANALYZE statements - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: pg_dump ANALYZE statements
Date
Msg-id 20070122232014.GT64372@nasby.net
Whole thread Raw
In response to pg_dump ANALYZE statements  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: pg_dump ANALYZE statements
List pgsql-hackers
On Mon, Jan 22, 2007 at 03:40:17PM +0000, Simon Riggs wrote:
> This would add a table-specific ANALYZE statement following each table's
> actions.

It'd probably be best to put it before any index creating activities,
since there's a better chance of everything from the table being in
shared buffers.

Better yet would be if COPY could analyze data as it was loaded in...
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: [GENERAL] Autovacuum Improvements
Next
From: Bruce Momjian
Date:
Subject: Re: [pgsql-patches] Win32 WEXITSTATUS too