| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Guo, Yun" <YGuo(at)cvent(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade from 9.3 to 9.4 fails |
| Date: | 2015-10-06 14:15:23 |
| Message-ID: | 20151006141523.GC9625@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, Oct 5, 2015 at 07:44:51PM +0000, Guo, Yun wrote:
> >My only guess is that when the server is running, you have started it
> >with some special options that pg_upgrade doesn't know about. If the
> >server is down, pg_upgrade has to start it to check it, and that might
> >be causing the problem. It would also be good to know if the failure is
> >with the old or new cluster.
>
> pg_upgrade_server.log outputs below message:
So you get the error:
ERROR: cache lookup failed for type 1670699
from pg_upgrade starting the server, but not when the server is already
running? I can't even guess what is wrong.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ramiro Barreca | 2015-10-06 15:39:49 | Randomly slow queries over TCP, but not on localhost |
| Previous Message | SELCUK AYDIN | 2015-10-06 10:20:21 | Re: postgresql services cant start |