Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZhBrT-0002Fc-Rz for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Sep 2015 07:31:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZhBrT-00027G-9t for pgsql-hackers@arkaria.postgresql.org; Wed, 30 Sep 2015 07:31:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZhBq8-0000cb-Ar for pgsql-hackers@postgresql.org; Wed, 30 Sep 2015 07:30:12 +0000 Received: from mail-qg0-x22c.google.com ([2607:f8b0:400d:c04::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZhBq5-0007yX-Da for pgsql-hackers@postgresql.org; Wed, 30 Sep 2015 07:30:11 +0000 Received: by qgx61 with SMTP id 61so27710579qgx.3 for ; Wed, 30 Sep 2015 00:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UezO8MeFu/NjuVelX8XRg8E/WbLJHuGoY+tFQMsv568=; b=pUqZE3xKHb0Z1jvhRdIV4DRvxoyAjGLiFCimZqPXUMqoQ+ypu1SHWQ4rHKUqz8Ki6B x9QLxjkTGPB4wLRXmWFoWYQ8TU0MlsKiL+VWnZl9YJVaTJagOZ/2z2Kh18cU8hqOS6NW elWvUf8aTO5FlItNOOgHDjLQkUiY5xUJCqa6YRxfoxmnQqx6RrCyF5aTu2rxc1clQTWH igNlhMw3DgBjb3NZWbCRPqjPjvS1rmUmRx9SabAVD29EfFUpUPAh3w+UeEGW56WfV5Py 4yiEhLSRSqy3XxRU9mTNYcyln67ew35nsOX6a39dZ0VGuVkkTnGeE9EAB8RTFoJKbwVH 9auQ== MIME-Version: 1.0 X-Received: by 10.140.96.84 with SMTP id j78mr2497154qge.94.1443598206357; Wed, 30 Sep 2015 00:30:06 -0700 (PDT) Received: by 10.140.21.50 with HTTP; Wed, 30 Sep 2015 00:30:06 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Sep 2015 16:30:06 +0900 Message-ID: Subject: Re: Standby server crashes in master and REL9_5_STABLE branches From: Michael Paquier To: oonishitk@nttdata.co.jp Cc: PostgreSQL mailing lists , Masao Fujii , Alvaro Herrera , Petr Jelinek Content-Type: multipart/alternative; boundary=001a113ab54449d5de0520f1e650 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --001a113ab54449d5de0520f1e650 Content-Type: text/plain; charset=UTF-8 On Wed, Sep 30, 2015 at 4:15 PM, wrote: > FATAL: could not access status of transaction 9009 > DETAIL: Could not read from file "pg_commit_ts/0000" at offset 90112: > Success. > CONTEXT: xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09 > LOG: startup process (PID 23199) exited with exit code 1 > LOG: terminating any other active server processes > > I cannot explain why but this crash seems to disappear if I moved HEAD to > before commit 6b61955135e94b39d85571fdbb0c5a749af767f1. > Even if I have the feeling that Alvaro, Petr and/or Fujii-san already know what is going on, do you have a backtrace at hand? -- Michael --001a113ab54449d5de0520f1e650 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Sep 30, 2015 at 4:15 PM, <oonishitk@nttdata.co.jp&g= t; wrote:
FATAL:=C2=A0 could not access status of transaction 9009
DETAIL:=C2=A0 Could not read from file "pg_commit_ts/0000" at off= set 90112: Success.
CONTEXT:=C2=A0 xlog redo Transaction/COMMIT: 2015-09-30 15:52:41.924141+09<= br> LOG:=C2=A0 startup process (PID 23199) exited with exit code 1
LOG:=C2=A0 terminating any other active server processes

I cannot explain why but this crash seems to disappear if I moved HEAD to b= efore commit 6b61955135e94b39d85571fdbb0c5a749af767f1.

Even = if I have the feeling that Alvaro, Petr and/or Fujii-san already know what = is going on, do you have a backtrace at hand?
--
Michael
--001a113ab54449d5de0520f1e650--