Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XbbLv-0002Wk-4c for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2014 20:27:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XbbLu-000690-K6 for pgsql-admin@arkaria.postgresql.org; Tue, 07 Oct 2014 20:27:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XbbLt-00067G-1C for pgsql-admin@postgresql.org; Tue, 07 Oct 2014 20:27:21 +0000 Received: from mail-yh0-x235.google.com ([2607:f8b0:4002:c01::235]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XbbLl-0002Bi-BP for pgsql-admin@postgresql.org; Tue, 07 Oct 2014 20:27:18 +0000 Received: by mail-yh0-f53.google.com with SMTP id b6so3304582yha.26 for ; Tue, 07 Oct 2014 13:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=+jmzjNwl0if5vhE1FnjT4bZqKP1NyCGu2ZdcIFYp6PA=; b=f/eucDSssNi4bbDoiGjFtmaS5tqplrJO6K/4FCE1K7xWO4S/xzEZ4uvlDOProiR4m9 hKy93zKAa1dPW90kWyiqcYzUEzQ2hTSGEdxcmj5cO2Ciq82HeXEn50H4LviulIT8c6Ug lO/pbbreobANOv5c9aK0qblVqxDPDLio6FUGJ26e6UxNimhjK4dKbjpd5tCopWpYZ/68 OZ1RSc51uKPGW3mwpXrSeL9kVjkgWLTqoGkQ6zbHfMEicY4dJJli5VoZ/NgelyehC7ZG lNAA1ckW0QpZqPUjZRksjsV8Pb2nM7xgKegRkVKWjitxlIuNRKPMG1GtwQvlaLJDHQzb AsKg== X-Received: by 10.236.84.230 with SMTP id s66mr890248yhe.13.1412713632195; Tue, 07 Oct 2014 13:27:12 -0700 (PDT) Received: from [192.168.254.2] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id h65sm8943080yhd.45.2014.10.07.13.27.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 13:27:11 -0700 (PDT) Message-ID: <54344C9E.9020508@gmail.com> Date: Tue, 07 Oct 2014 16:27:10 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Restart or reload after changing the archive_command Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 I've been looking online for an answer, as my test environment is currently unavailable due to an upgrade, but while I know ('cuz it says in the conf file) that a restart is required when you change "archive_mode", is a restart or a reload required if the "archive_command" is changed? I seem to recall previously that I issued a reload after I changed this parameter and I saw in the logs that the new value had been recorded, but I'm not certain. -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin