Re: server closed the connection unexpectedly during upgrade

But the issue not reproducing regularly can affect our upgrade project. The attached log files shows log error. Sometimes the issue reproduces when run pg_upgrade check from PostgreSQL 8.3 to PostgreSQL 9.4.5, but it will succeed sometimes.

Regards,
Leo

-----Original Message-----
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
Sent: 2015年12月16日 15:58
To: Yang, Leo
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: server closed the connection unexpectedly during upgrade

On Wed, Dec 16, 2015 at 4:34 PM, Yang, Leo <leo(dot)yang(at)hp(dot)com> wrote:
> Hi all,
>
> Thank you for your explain for previous question. But I met another error log when running pg_upgrade check from PostgreSQL 8.3 to PostgreSQL 9.4.5:
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> Checking database user is a superuser ok
> Checking database connection settings ok
> Checking for prepared transactions ok
> Checking for reg* system OID user data types ok
> Checking for contrib/isn with bigint-passing mismatch ok
> Checking for invalid "name" user columns connection to database failed: server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> This issue don't reproduces regularly on windows Server 2012. The error log only reproduces in a few cases, but I need to fix this issue. Can you tell me the reasons for this error.

There is no way to know what actually happened without the server logs, that's where the problem visibly happened..
--
Michael