Re: analyze after a database restore?
| От | Alvaro Herrera |
|---|---|
| Тема | Re: analyze after a database restore? |
| Дата | |
| Msg-id | 20030227224411.GA10724@dcc.uchile.cl обсуждение |
| Ответ на | Re: analyze after a database restore? (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On Thu, Feb 27, 2003 at 03:12:36PM -0500, Tom Lane wrote: > Although I suggested doing a single unconditional ANALYZE at the end > of the script, second thought leads me to think the per-table ANALYZE > (probably issued right after the table's data-load step) might be > better. That way you'd not have any side-effects on already-existing > tables in the database you are loading to. OTOH, that way would leave > the system catalogs un-analyzed, which might be bad. Huh... is there a way to analyze a specific schema? Maybe that can solve the problem of system catalogs being left un-analyzed, by having pg_dump emit an "ANALYZE SCHEMA pg_catalog" or something. -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>) "La libertad es como el dinero; el que no la sabe emplear la pierde" (Alvarez)
В списке pgsql-hackers по дате отправления: