pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Yang, Leo <leo.yang@hp.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: pgsql-bugs@postgresql.org <pgsql-bugs@postgresql.org>
Subject: Re: server closed the connection unexpectedly during upgrade
Date: Wed, 16 Dec 2015 08:26:54 +0000
Message-ID: <DF4PR84MB02341A93373A6C9D96E20369F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAB7nPqR_WJ0xVs-T6ZkiHVnDc9f13az_Wq8wWveae6m4zXBvEQ@mail.gmail.com>
References: <DF4PR84MB023427226CC33BBC54E8A418F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM>
	<CAB7nPqR_WJ0xVs-T6ZkiHVnDc9f13az_Wq8wWveae6m4zXBvEQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>

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.paquier@gmail.com] 
Sent: 2015年12月16日 15:58
To: Yang, Leo
Cc: pgsql-bugs@postgresql.org
Subject: Re: server closed the connection unexpectedly during upgrade

On Wed, Dec 16, 2015 at 4:34 PM, Yang, Leo <leo.yang@hp.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


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Attachments:

  log file.rar (application/octet-stream, 1.5K) download

view thread (19+ messages)  latest in thread

Message-ID: <DF4PR84MB02341A93373A6C9D96E20369F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM>
Permalink:  ../DF4PR84MB02341A93373A6C9D96E20369F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM/
Also on:    postgresql.org/message-id/DF4PR84MB02341A93373A6C9D96E20369F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: leo.yang@hp.com, michael.paquier@gmail.com
  Subject: Re: server closed the connection unexpectedly during upgrade
  In-Reply-To: <DF4PR84MB02341A93373A6C9D96E20369F4EF0@DF4PR84MB0234.NAMPRD84.PROD.OUTLOOK.COM>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox