Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aWWVd-0007JD-Np for pgsql-admin@arkaria.postgresql.org; Thu, 18 Feb 2016 21:53:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aWWVd-0005Do-AU for pgsql-admin@arkaria.postgresql.org; Thu, 18 Feb 2016 21:53:13 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aWWVc-0005CW-Kk for pgsql-admin@postgresql.org; Thu, 18 Feb 2016 21:53:12 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aWWVZ-0000bU-C2 for pgsql-admin@postgresql.org; Thu, 18 Feb 2016 21:53:12 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u1ILr1WH027146; Thu, 18 Feb 2016 16:53:01 -0500 From: Tom Lane To: Bruce Momjian cc: Evan Rempel , pgsql-admin@postgresql.org Subject: Re: 9.5 new setting "cluster name" and logging In-reply-to: <20160218214202.GA30326@momjian.us> References: <1377186808.57546.YahooMailNeo@web193505.mail.sg3.yahoo.com> <1377494614.9111.YahooMailNeo@web193506.mail.sg3.yahoo.com> <56AC5601.5040208@uvic.ca> <20160218214202.GA30326@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 18 Feb 2016 16:42:02 -0500" Date: Thu, 18 Feb 2016 16:53:01 -0500 Message-ID: <27145.1455832381@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Bruce Momjian writes: > On Fri, Jan 29, 2016 at 10:19:45PM -0800, Evan Rempel wrote: >> Now that there is a setting to give a cluster a "name", it would be >> nice to have an escape sequence in the log_line_prefix setting that >> could reference the cluster_name. > Uh, wouldn't the cluster name be the same on every line? Is that > useful? I guess if you were running multiple clusters and having them all log to the same syslog daemon, there might be multiple clusters' output in the same log ... but we already have ways to disambiguate that case, ie, syslog_ident. Likewise for Windows' event log. I don't think we should consider it supported for multiple clusters to be logging into the same plain files. So yeah, the use case for this seems unclear. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin