Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 4B7556322E0 for ; Thu, 3 Jun 2010 04:45:53 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 71056-07 for ; Thu, 3 Jun 2010 07:45:45 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-px0-f174.google.com (mail-px0-f174.google.com [209.85.212.174]) by mail.postgresql.org (Postfix) with ESMTP id 58B126321B1 for ; Thu, 3 Jun 2010 04:45:45 -0300 (ADT) Received: by pxi8 with SMTP id 8so347169pxi.19 for ; Thu, 03 Jun 2010 00:45:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:organization:user-agent :x-operating-system:x-face:face:x-mailer:mime-version:content-type :content-transfer-encoding; bh=2an4rgY6PWtk+fUCQY/2kojuUimT5yAd+C6goKXDD6U=; b=r1rJFKtCmF3Y4c1VzubgflYtA8Ixz1VKnnDS+uR5IeDcbiXLDTFdi6/foTpn+SYa+F H7B9ftQ8A8C7L/nuY0NgXnhzIALqGdqx5dlmFLrjtIpiCg8KoAFfIR6j/UboaV1Qxwpf gefSQL7veHJCDYvM+1ZpdOrgIWmqcAlAHOpwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:user-agent:x-operating-system:x-face:face:x-mailer :mime-version:content-type:content-transfer-encoding; b=TEl7FhZDtueSptU11AwXrsFqBXU0Bja/B8WCVUH8koFit5uhTkvQfPcQKI7cy027K4 miB3mcLxCWELI8KCsBO+fDO45fiIlVd7hj0cqMNbKiLCWq5psPD9Yk4jndzZhNRiGrb3 E93mELiy87Aa+9Q8CqNcFcixuhehptIkVkkcg= Received: by 10.142.55.7 with SMTP id d7mr6229588wfa.344.1275551143598; Thu, 03 Jun 2010 00:45:43 -0700 (PDT) Received: from icy.localdomain ([115.78.0.218]) by mx.google.com with ESMTPS id e40sm2901753wfj.11.2010.06.03.00.45.41 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Jun 2010 00:45:43 -0700 (PDT) Date: Thu, 3 Jun 2010 14:45:28 +0700 From: "Anh Ky Huynh" To: v.tolstov@selfip.ru Cc: PostgreSQL Admin Subject: Re: graceful reload Message-ID: <20100603144528.2234301e@icy.localdomain> In-Reply-To: <1275546216.6693.2.camel@work.selfip.ru> References: <1275546216.6693.2.camel@work.selfip.ru> Organization: Vietnamese TeX Users Group User-Agent: FreeBSD X-Operating-System: FreeBSD X-Face: FreeBSD Face: FreeBSD X-Mailer: FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.217 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77 X-Spam-Level: X-Archive-Number: 201006/25 X-Sequence-Number: 34803 On Thu, 03 Jun 2010 10:23:36 +0400 Vasiliy G Tolstov wrote: > Hello. > > I'm use linux and postgresql under xen vps. Vps supports memory > balloon (i need to increase memory some time). Can postgresql > server has ability to graceful reload itself after it configuration > files changed? Thank You. I'm afraid *NOT*. You can write a script / cronjob for this task. The script will check postgresql periodically and will restart posgresql daemon in case the configuration was changed. You can use `stat` command (try `stat --help`) to get the right information about file's modifcation. You should *check* if your configuration is valid before restart the daemon as any wrong modification can cause your server to stop :) I know there's a tool that will do some tasks whenever a(ny) file in the system has been modified. But I can't remember the name of that tool. Regards, -- Anh Ky Huynh