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.94.2) (envelope-from ) id 1vFtuu-003BdL-D1 for pgsql-docs@arkaria.postgresql.org; Mon, 03 Nov 2025 12:44:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vFtut-003Edx-AN for pgsql-docs@arkaria.postgresql.org; Mon, 03 Nov 2025 12:44:10 +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.94.2) (envelope-from ) id 1vFtut-003Edp-3I for pgsql-docs@lists.postgresql.org; Mon, 03 Nov 2025 12:44:10 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vFtuo-005DPO-3C for pgsql-docs@lists.postgresql.org; Mon, 03 Nov 2025 12:44:09 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 3315C4B0144 for ; Mon, 03 Nov 2025 13:44:03 +0100 (CET) Received: from s981.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 23DB24B0423; Mon, 03 Nov 2025 13:44:03 +0100 (CET) Received: from localhost (unknown [172.22.191.5]) by s981.loopia.se (Postfix) with ESMTP id 19D8E22B1701; Mon, 03 Nov 2025 13:44:03 +0100 (CET) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 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, URI_NOVOWEL=0.5] autolearn=disabled Authentication-Results: s898.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s899.loopia.se ([172.22.191.5]) by localhost (s898.loopia.se [172.22.190.17]) (amavis, port 10024) with UTF8LMTP id 5q20LVmHDiKL; Mon, 3 Nov 2025 13:44:02 +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 0A8A02C8BA86; Mon, 03 Nov 2025 13:44:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1762173842; bh=M1SY1nckdcID66Yi/S4qCoTvDnn6IqTYtz6ShG8LbRs=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=cwqMUwVOxF69x2kmZ7UQTztBDPa4UYRpnGcRscVKj+Q+X+accWpC7KK1Z7gQmReqH qfXGaw5pEVPS85RZnwNdRbTRajBA9665+04ZPXaPhSmjbdPXOKI4oYHqQrvCNcjxXr IKvOCLEr0ZSvdQ5V5cA7Cfpd9/PV9keN/m6WYGsD3cxz7SGh0hUAOe9T0EaZQEzSUt 4gV+gk3yp6AegrHMgxezJXhI9B6G85+5KDL7DqdWPUzibXcjE456Mw7mha+TLIp5iY xZqjYOZfIWpuzkNgp2DmqTljsXNBeBxF+GplAOpDWpQIVlOEhWqHh0oYvMahlMInbZ FOBIasI4YDDGA== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: Feature request: Add a llms.txt file to the docs for AIs to learn From: Daniel Gustafsson In-Reply-To: Date: Mon, 3 Nov 2025 13:43:51 +0100 Cc: pgsql-docs@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: =?utf-8?Q?Adri=C3=A1n_Cuadrado_Chavarr=C3=ADa?= 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 2 Nov 2025, at 00:47, Adri=C3=A1n Cuadrado Chavarr=C3=ADa = wrote: >=20 > Some projects like [NextJS](https://nextjs.org/docs/llms-full.txt), = [Stripe](https://docs.stripe.com/llms.txt), = [BetterAuth](https://www.better-auth.com/llms.txt) and = [Zod](https://zod.dev/llms.txt) already provide this.=20 >=20 > With this file we can make sure that the AI model fetching it is = always using the latest features and versions of postgresql. >=20 > https://llmstxt.org/ I would recommend posting this to the pgsql-www@ mailinglist instead to = get the attention of the website team. That being said, AFAICT there are no LLM providers who have publicly = stated that they are using this proposed standard at all, and the author has = not submitted it to IETF for a formal review in the RFC process, so it = doesn't seem all that promising. -- Daniel Gustafsson