Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppmSn-00032D-4m for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Apr 2023 08:49:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ppmSm-0008Sl-3G for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Apr 2023 08:49:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ppmSl-0008Sc-Q4 for pgsql-hackers@lists.postgresql.org; Fri, 21 Apr 2023 08:49:51 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ppmSj-004CWV-RL for pgsql-hackers@lists.postgresql.org; Fri, 21 Apr 2023 08:49:51 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 19B7C2F7755B for ; Fri, 21 Apr 2023 10:49:49 +0200 (CEST) Received: from s934.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 0A8D42E27D5B; Fri, 21 Apr 2023 10:49:49 +0200 (CEST) Received: from s472.loopia.se (unknown [172.22.191.6]) by s934.loopia.se (Postfix) with ESMTP id 049DE7CEA7E; Fri, 21 Apr 2023 10:49:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s980.loopia.se ([172.22.191.6]) by s472.loopia.se (s472.loopia.se [172.22.190.12]) (amavisd-new, port 10024) with LMTP id Y5RPE6B9KXSU; Fri, 21 Apr 2023 10:49:48 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s980.loopia.se (Postfix) with ESMTPSA id 80C482201616; Fri, 21 Apr 2023 10:49:48 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\)) Subject: Re: [PATCH] Extend the length of BackgroundWorker.bgw_library_name From: Daniel Gustafsson In-Reply-To: <20230420233243.GB1437940@nathanxps13> Date: Fri, 21 Apr 2023 10:49:48 +0200 Cc: Yurii Rashkovskii , pgsql-hackers@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20230313173528.GA195204@nathanxps13> <20230420233243.GB1437940@nathanxps13> To: Nathan Bossart X-Mailer: Apple Mail (2.3696.120.41.1.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 21 Apr 2023, at 01:32, Nathan Bossart = wrote: >=20 > On Wed, Mar 15, 2023 at 10:38:34AM +0100, Daniel Gustafsson wrote: >> While here, I wonder if we should document what BGW_MAXLEN is defined = as in >> bgworker.sgml? >=20 > I am -0.5 for this. If you are writing a new background worker, it's > probably reasonable to expect that you can locate the definition of > BGW_MAXLEN. =20 Of course. The question is if it's a helpful addition for someone who = is reading the documentation section on implementing background workers = where we explicitly mention BGW_MAXLEN without saying what it is. > Also, I think there's a good chance that we'd forget to update > such documentation the next time we adjust it. There is that, but once set to MAXPGPATH it seems unlikely to change particularly often so it seems the wrong thing to optimize for. -- Daniel Gustafsson