Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvwCV-0003Lo-Ph for pgsql-admin@arkaria.postgresql.org; Thu, 17 Jan 2013 20:36:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TvwCT-0005Sr-TV for pgsql-admin@arkaria.postgresql.org; Thu, 17 Jan 2013 20:36:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvwCT-0005Sm-4w for pgsql-admin@postgresql.org; Thu, 17 Jan 2013 20:36:37 +0000 Received: from qmta08.emeryville.ca.mail.comcast.net ([2001:558:fe2d:43:76:96:30:80]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TvwCR-00033B-8Z for pgsql-admin@postgresql.org; Thu, 17 Jan 2013 20:36:36 +0000 Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta08.emeryville.ca.mail.comcast.net with comcast id p8Y91k0011u4NiLA88cZRG; Thu, 17 Jan 2013 20:36:33 +0000 Received: from homie ([38.98.177.132]) by omta21.emeryville.ca.mail.comcast.net with comcast id p8cQ1k00h2rmZlA8h8cTiK; Thu, 17 Jan 2013 20:36:31 +0000 Received: by homie (Postfix, from userid 1000) id 6098F1815CA; Thu, 17 Jan 2013 15:36:24 -0500 (EST) Subject: Escaping a blocked sendto() syscall without causing a restart To: pgsql-admin@postgresql.org From: Jerry Sievers Date: Thu, 17 Jan 2013 14:36:24 -0600 Message-ID: <87obgnczsn.fsf@comcast.net> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1358454993; bh=pJoK0BP9RWaWNPCJxSh0K+SV7Glw4pvPeAj8E+CLJoA=; h=Received:Received:Received:Subject:To:From:Date:Message-ID: MIME-Version:Content-Type; b=oa6iK9SeBXrNInWN3cB1qyU5lbIN2W0rdsOB45k3Nt9Ow8/aVJ1lgbzniurbwx2v6 Bj+3W1h4YMxf7wbwmz0XPU1D/r/LEFVaOJqPtWYdJgE3VWp+SLoMFQbvFHZoqzelsD tgU6Xl06vZWWIPnH86FqE6KpOCIjq5WcItD7xi4n+UTAtvXEo/ioy2TeQNHnIG37vn hm9/B0zrGGZeFfs5uQWHQlt3kwcMN/eqwPxnTGacfUJmUgT7c69CHN4rsQp9JiQmJZ NoKDqPsIAUqfsWm/X7cDzBGZg/JLZfBgUIHaBhKPPHIEEzGs2t/zXKcYyra8HR1k1M tMFJ3KJ2vxjww== X-Pg-Spam-Score: -0.8 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Does anyone know if one of the signals below can be sent to break out ,of this state *without* the postmaster sensing a crashed backend? I've seen several times in the past at other companies, backends that will not respond to cancel nor SIGTERM due to syscall that's blocked on IO. Quite often though apparently the backend would notice the broken socket eventually and receive the signals and exit cleanly. I've got one that's been wedged like that for a couple days now. I recall trying several in a similar situation a while ago and of course one of them interrupted the syscall all right but it was an abort and we got the customary spontaneous postmaster restart. PostgreSQL 8.4.13 on x86_64-pc-linux-gnu, compiled by GCC gcc-4.3.real (Debian 4.3.2-1.1) 4.3.2, 64-bit $ uname -a Linux somebox.foo.zizzy 2.6.36 #5 SMP Thu Jul 28 17:52:31 UTC 2011 x86_64 GNU/Linux $ $ strace -p 31603 Process 31603 attached - interrupt to quit sendto(9, "default_rate_3m_v4: 0.1224\nmonth_"..., 3440, 0, NULL, 0 Process 31603 detached $ $ $ kill -l 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL 5) SIGTRAP 6) SIGABRT 7) SIGBUS 8) SIGFPE 9) SIGKILL 10) SIGUSR1 11) SIGSEGV 12) SIGUSR2 13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGSTKFLT 17) SIGCHLD 18) SIGCONT 19) SIGSTOP 20) SIGTSTP 21) SIGTTIN 22) SIGTTOU 23) SIGURG 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGIO 30) SIGPWR 31) SIGSYS 34) SIGRTMIN 35) SIGRTMIN+1 36) SIGRTMIN+2 37) SIGRTMIN+3 38) SIGRTMIN+4 39) SIGRTMIN+5 40) SIGRTMIN+6 41) SIGRTMIN+7 42) SIGRTMIN+8 43) SIGRTMIN+9 44) SIGRTMIN+10 45) SIGRTMIN+11 46) SIGRTMIN+12 47) SIGRTMIN+13 48) SIGRTMIN+14 49) SIGRTMIN+15 50) SIGRTMAX-14 51) SIGRTMAX-13 52) SIGRTMAX-12 53) SIGRTMAX-11 54) SIGRTMAX-10 55) SIGRTMAX-9 56) SIGRTMAX-8 57) SIGRTMAX-7 58) SIGRTMAX-6 59) SIGRTMAX-5 60) SIGRTMAX-4 61) SIGRTMAX-3 62) SIGRTMAX-2 63) SIGRTMAX-1 64) SIGRTMAX $ Thanks -- Jerry Sievers e: jerry.sievers@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin