Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jBh0g-000120-2w for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Mar 2020 15:41:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jBh0e-0006ze-UV for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Mar 2020 15:41:32 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1jBh0e-0006zW-LY for pgsql-hackers@lists.postgresql.org; Tue, 10 Mar 2020 15:41:32 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jBh0a-0000ZM-T2 for pgsql-hackers@postgresql.org; Tue, 10 Mar 2020 15:41:31 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E8B5B305; Tue, 10 Mar 2020 11:41:25 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 10 Mar 2020 11:41:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=j2LhiLs7g/AzF5Og+Hul578oGmKk2J1dVBKlY17uk 4A=; b=1kCZyqCpJpZDL35wVh+LvLM2VELzE32095nQjETqpMNM8NmYnE0xA5Iq3 1sCh1qSvazg1RbBYgnZd9R3vAYqNoy601fFnzAYAYqpmDSYHMCRv7ERuCRUWx2AT kqmoDA5nuMaSTFu0fsmMR7Uvvf/T5IHXhYTKbLFfE1P9Jc4+6cbA0Vyl69NlYpzn gVL2tjomOE3GIABs98kJ6OC4//VRSalfMtyQvXBnu7FBfOs99Zvv+uWOd4YKdSQH Y3Wwj0r4BMJnSz6vlyuELYM4T44CvfC9JedTVM2m84D9Ol+hAVVxz1UK8GZtNswR tM4J89L44vD+G5p9EhPV5FWUnmF1w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvtddgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegvddrvddufedrvdegudenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df2d5f1.dip0.t-ipconnect.de [93.242.213.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 628AC3061393; Tue, 10 Mar 2020 11:41:24 -0400 (EDT) Subject: Re: backend type in log_line_prefix? To: Kuntal Ghosh References: <6453e044-041a-bf64-c76a-e1b7e3d5b0e7@2ndquadrant.com> Cc: pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <26fb28aa-b614-e3ca-344b-d98058496d52@2ndquadrant.com> Date: Tue, 10 Mar 2020 16:41:23 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-03-09 16:20, Kuntal Ghosh wrote: > In v3-0001-Refactor-ps_status.c-API.patch, > > - * > - * For a walsender, the ps display is set in the following form: > - * > - * postgres: walsender > This part is still valid, right? Sure but I figured this comment was in the context of the explanation of how the old API was being abused, so it's no longer necessary. > + init_ps_display(ps_data.data); > + pfree(ps_data.data); > + > + set_ps_display("initializing"); > As per the existing behaviour, if update_process_title is true, we > display "authentication" as the initial string. On the other hand, > this patch, irrespective of the GUC variable, always displays > "initializing" as the initial string and In PerformAuthentication, it > sets the display as "authentication" Is this intended? Should we check > the GUC here as well? set_ps_display() checks update_process_title itself and does nothing if it's off, so this should work okay. > In v3-0002-Unify-several-ways-to-tracking-backend-type.patch, > + * If fixed_part is NULL, a default will be obtained from BackendType. > s/BackendType/MyBackendType? yup > In v3-0003-Add-backend-type-to-csvlog-and-optionally-log_lin.patch, > + Backend process type > In other places you've written "backend type". ok changed > > In v3-0004-Remove-am_syslogger-global-variable.patch, > + * This is exported so that elog.c can call it when BackendType is B_LOGGER. > s/BackendType/MyBackendType? ok -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services