Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40866=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1UPEWo-0004XS-91
	for pgsql-admin@arkaria.postgresql.org; Mon, 08 Apr 2013 16:02:42 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M40866=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1UPEWn-0004Lr-Ps
	for pgsql-admin@arkaria.postgresql.org; Mon, 08 Apr 2013 16:02:41 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <kakalot49@gmail.com>) id 1UPEWn-0004Lm-2C
	for pgsql-admin@postgresql.org; Mon, 08 Apr 2013 16:02:41 +0000
Received: from mail-oa0-f45.google.com ([209.85.219.45])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <kakalot49@gmail.com>) id 1UPEWj-0003QJ-8O
	for pgsql-admin@postgresql.org; Mon, 08 Apr 2013 16:02:40 +0000
Received: by mail-oa0-f45.google.com with SMTP id o6so6239707oag.4
	for <pgsql-admin@postgresql.org>; Mon, 08 Apr 2013 09:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:message-id:date:from:user-agent:mime-version:to:subject
	:content-type; bh=f4QX+EBSM1HFcwm6umF7VUOKXUi0ZJ6OlqPS/Ah1W/Q=;
	b=KPN7mtfDKGKf0yn/Kyg90gyzvz+2hzhrmxYc7WhzDJDblNroya0gpZ58FZDZDs4qU+
	TvPEWeI7BHpuy2Zge5Gu3w6XaqVv1unn4NXTami2X3PUOJ4z4za5z29xxbnANlMmZlXX
	P8+5YeqgYyr0lVCMT4s9nuA7I4dJpM+1Jk5KdQ1DDIEANVuGpbQe80RI4HrZBHEZ+IRL
	ZnZ7KI2klL9XW9o3se3swNN6XH614PbaGScUNbLZg1fib6zjpfh0X0Zsh7rexcAVV1sI
	w+L+arQ9kyYOLYplG/jAJkF0AaXJanP9tRMWyJJfiAVVNQEnCwpjkGXMpkpjiiR/RyZe
	2VPw==
X-Received: by 10.60.19.228 with SMTP id i4mr4688436oee.45.1365436956241;
	Mon, 08 Apr 2013 09:02:36 -0700 (PDT)
Received: from [192.168.0.5] (KD106178052085.ppp-bb.dion.ne.jp.
	[106.178.52.85])
	by mx.google.com with ESMTPS id zc8sm24703739obc.8.2013.04.08.09.02.33
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 08 Apr 2013 09:02:35 -0700 (PDT)
Message-ID: <5162EA18.9010802@gmail.com>
Date: Tue, 09 Apr 2013 01:02:32 +0900
From: Dang Minh Huong <kakalot49@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: how to terminate hang up sender process
Content-Type: multipart/alternative;
	boundary="------------030504000904020203080609"
X-Pg-Spam-Score: -2.4 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.
--------------030504000904020203080609
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

Hi all,

I'm using PostgreSQL 9.1.7's replication function for my HA project
and getting trouble when terminate the hangup sender process.

My cluster configuration: Node1(MASTER) Node2(STANDBY)

Execution sequence:
---
step 1.
execute pg_basebackup on Node2

step 2.
While Node2's pg_basebackup is processing (wal sender was
created in Node1), turn off the Node2 by power off buton.
---

Problem:
---
the sender process in Node1 for base_backup of Node2(SLAVE)
was hanging up (in about 30 minutes).
---

Question:
---
Is there's a solution to terminate that [wal sender] in Node1 but not
restart or kill (-9) the process?
---

I've tried with replication_timeout=60s (default)

best regards,
Huong DM.

--------------030504000904020203080609
Content-Type: text/html; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-2022-JP">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi all,<br>
    <br>
    I'm using PostgreSQL 9.1.7's replication function for my HA project
    <br>
    and getting trouble when terminate the hangup sender process.<br>
    <br>
    My cluster configuration: Node1(MASTER) Node2(STANDBY)<br>
    <br>
    Execution sequence:<br>
    ---<br>
    &nbsp;step 1.<br>
    &nbsp;execute pg_basebackup on Node2<br>
    <br>
    &nbsp;step 2.<br>
    &nbsp;While Node2's pg_basebackup is processing (wal sender was <br>
    &nbsp;created in Node1), turn off the Node2 by power off buton.<br>
    ---<br>
    <br>
    Problem:<span style="color: rgb(0, 0, 0); font-family: 'ＭＳ Ｐゴシック',
      arial, sans-serif; font-size: 14px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: 25.90625px; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto;
      -webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
      255); display: inline !important; float: none;"></span><br>
    ---<br>
    the sender process in Node1 for base_backup of Node2(SLAVE)<br>
    was hanging up (in about 30 minutes).<br>
    ---<br>
    <br>
    Question:<br>
    ---<br>
    Is there's a solution to terminate that [wal sender] in Node1 but
    not<br>
    restart or kill (-9) the process?<br>
    ---<br>
    <br>
    I've tried with replication_timeout=60s (default)<br>
    <br>
    best regards,<br>
    Huong DM.<br>
  </body>
</html>

--------------030504000904020203080609--