| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is analyze_new_cluster.sh still useful? |
| Date: | 2014-07-29 09:42:34 |
| Message-ID: | 20140729094234.GC13958@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 20, 2014 at 05:15:05PM +0200, Christoph Berg wrote:
> Another nitpick here: What pg_upgrade outputs doesn't even work on
> most systems, you need to ./analyze_new_cluster.sh or "sh
> analyze_new_cluster.sh".
Well, the output is:
Optimizer statistics are not transferred by pg_upgrade so,
once you start the new server, consider running:
analyze_new_cluster.sh
Running this script will delete the old cluster's data files:
delete_old_cluster.sh
It is not really telling you _how_ to run them. Would adding a ./
prefix help?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | furuyao | 2014-07-29 10:07:00 | Re: pg_receivexlog add synchronous mode |
| Previous Message | Bruce Momjian | 2014-07-29 09:38:55 | Re: Is analyze_new_cluster.sh still useful? |