Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dfVWF-0006as-0Y for pgsql-performance@arkaria.postgresql.org; Wed, 09 Aug 2017 18:15:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dfVWE-0007HM-Eh for pgsql-performance@arkaria.postgresql.org; Wed, 09 Aug 2017 18:15:46 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dfVWD-0007H0-Jt for pgsql-performance@postgresql.org; Wed, 09 Aug 2017 18:15:45 +0000 Received: from resqmta-ch2-03v.sys.comcast.net ([2001:558:fe21:29:69:252:207:35]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dfVWA-0003Km-Bu for pgsql-performance@postgresql.org; Wed, 09 Aug 2017 18:15:44 +0000 Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id fVV0dHHdadtjefVW8d13Md; Wed, 09 Aug 2017 18:15:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1502302540; bh=AP320I6OI26khmHcefek7FJxIjC20XoQnhLWnTF8k9Q=; h=Received:Received:To:From:Subject:Message-ID:Date:MIME-Version: Content-Type; b=LFAnetWWERRzGFsMdYBLN4vRk9xEHH2Q36Ae+3KI7D46t52BhDnnQP/HUYEVuMjgf lHR6CFgkHwj2eij8xMIBJFcS/RcxKLEuLKGT4+kdHYqXNj1expDfNxcAZGhzz1oJOA Gu/YJQ3zgFmMgfc4p3qDdrWrC+L031NqMpZWQNrgG0QrzLWrCB04tFfxjr+8F52u/r lO9tX0bl6tNc4rqVKmYvm5OEWTYX3o/dM1Q2puJwB0yeMSguDHNLxj6UxqCs4wVVpr nh7lc/XCPRUH7uUuq9VxmfdebtWm/7BtYcx4GM0eOYm2uGAAxZY39dJMdQrjK0Mb/g 35VHquauiJKig== Received: from [192.168.0.67] ([73.68.146.26]) by resomta-ch2-16v.sys.comcast.net with SMTP id fVW7dKXR3eaimfVW7djaAW; Wed, 09 Aug 2017 18:15:40 +0000 To: pgsql-performance@postgresql.org From: George Neuner Subject: Re: Unlogged tables Message-ID: <314ce53a-ee57-0be3-7815-f0e99fc0a6e4@comcast.net> Date: Wed, 9 Aug 2017 14:15:37 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-CMAE-Envelope: MS4wfLjMqGmVqdXDbNhccl3LsbxBwcQG8+GZR7uX+zVuJwJcKOX40GVkGpAajnCMxFgPZkuv3F7djVfRK/bFWkHcgDaGx3panXEKeLbRpJ4ffX8dpwg4lndq rKZyoBR2TgoKFB/aGZvMMz/ZXIrQi6+CyZbdFxpyrlc7h3xxxsxLHgrR+w5TuKRBG80ADbZoGJSwHw== List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Wed, 9 Aug 2017 09:14:48 -0700, Jeff Janes wrote: >Why doesn't the Windows scheduled shutdown signal postgres to shutdown >cleanly and wait for it to do so? That is what is supposed to happen. Windows *does* signal shutdown (and sleep and hibernate and wakeup). pg_ctl can catch these signals only when running as a service ... it will not catch any system signals when run as an application. George -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance