Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vyGw5-00Ha96-1j for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Mar 2026 22:12:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vyGw3-001g2R-33 for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Mar 2026 22:12:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vyGw3-001g2J-1n for pgsql-hackers@lists.postgresql.org; Thu, 05 Mar 2026 22:12:48 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vyGw1-00000000fsL-0HQ5 for pgsql-hackers@lists.postgresql.org; Thu, 05 Mar 2026 22:12:47 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id C9EAF572A18 for ; Thu, 05 Mar 2026 23:12:40 +0100 (CET) Received: from s934.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id B6764572E5B; Thu, 05 Mar 2026 23:12:40 +0100 (CET) Received: from s474.loopia.se (unknown [172.22.191.5]) by s934.loopia.se (Postfix) with ESMTP id B4CA17CEA64; Thu, 05 Mar 2026 23:12:40 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s899.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id QeRajRoIzjBZ; Thu, 5 Mar 2026 23:12:40 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s899.loopia.se (Postfix) with ESMTPSA id 3978D2C8BA8D; Thu, 05 Mar 2026 23:12:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1772748760; bh=Fk2F0TTw4/Kkji0uzsmXnHJzBzLQSqJcRND1Y5bsvJM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=q1ljLZn70bHbSVt6Yej1NwBDAV0AlprXf8sXF8/3nKsVPdEGBopCUiwanfyQqyU+c CpqYstppsAaouKXz0hDbvod+i3Q9PVRHNn/S1fOc9PM/xgmSH+IL2PTXntLI+YTkjQ DNPS/cy3O1Tcn6hAua31owIDctPTZAsbek4TT2nb5QSuQH13gUUjrKarQJaENslNoz NL8qVqIXFdOB4LyZAGrzAh1wYiF6C2T0kHXOvet2ANPXv2rkmyYhgXeCa5TAlXz5MG UJqkv6aSzym0Fztf5qGf8fiQNUTrBb4a8ZetrCgaBrW8bd098/fIklZFDE/ENZs+7Y Hgh9o6fUmFyaw== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: on SGML files is used for what ? From: Daniel Gustafsson In-Reply-To: Date: Thu, 5 Mar 2026 23:12:29 +0100 Cc: PostgreSQL Hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Marcos Pegoraro X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 5 Mar 2026, at 19:53, Marcos Pegoraro wrote: >=20 > Yesterday, Michael Paquier submitted this correction: > Revert "Change the default value of default_toast_compression to = "lz4"" > which is in the installation.sgml has: > Build with LZ4 compression = support. > But other SGML files on that commit are all using literal tag. > So I thought, LZ4 is not a product name, so where else is this tag = used ? > And that tag is used for Kerberos, Zstandard, GSSAPI, SSPI, Windows, = Oracle and others. So, there are company names, programs, protocols, = utilities and others. The DocBook manual is the main source for truth about when to use the = various tags, is documented in [1]. So Oracle is clearly a = productname if it refers to the database and not the company, but Windows should = probably use [1] instead. Whether or not LZ4 is a = product name feels harder to define, but it doesn't seem entirely wrong, = especially not for the installation docs. Mind you, we aren't using the tagging exactly according to the = specification so appropriate levels of salt should be applied, for example = is meant to be used for larger software packages whereas we apply it = pg_dump etc. > Do these need to use the tag, or do we need an additional = one, or perhaps a tag for each of these types ? is IMHO great for tagging text to indicate that it is expected = system input/output or source code. Depending on context, lz4 could absolutely = use (but personally I think we should be careful to not overuse ). -- Daniel Gustafsson [0] https://tdg.docbook.org/tdg/5.0/productname.html [1] https://tdg.docbook.org/tdg/5.0/systemitem.html=