Re: Feature request: Add a llms.txt file to the docs for AIs to learn
On Sun, 2025-11-02 at 00:47 +0100, Adrián Cuadrado Chavarría wrote: > 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. > > With this file we can make sure that the AI model fetching it is always using > the latest features and versions of postgresql. > > https://llmstxt.org/ Why should we invest effort to feed the machine? I don't think that that improves life for anybody, except perhaps for the owners of said LLMs. Yours, Laurenz Albe
Re: Feature request: Add a llms.txt file to the docs for AIs to learn
> Why should we invest effort to feed the machine? Great news: you don't have to. I don't mind investing the effort myself so no one else has to. It's just a matter of creating a script that would concatenate all markdown files of the documentation and run it automatically whenever a change is made in any document. > I don't think that that improves life for anybody, except perhaps for the owners of said LLMs. Users of LLMs would appreciate having a feature like this one. But really, it's just a feature request, not a command or an order. If more people agree that it wouldn't be a good idea to have something like this then I'll just stop pushing it. If some others think this would be a nice thing to have then maybe it would be worth it to make this real. On Sun, Nov 2, 2025 at 9:58 AM Laurenz Albe wrote: > On Sun, 2025-11-02 at 00:47 +0100, Adrián Cuadrado Chavarría wrote: > > 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. > > > > With this file we can make sure that the AI model fetching it is always > using the latest features and versions of postgresql. > > > > https://llmstxt.org/ > > Why should we invest effort to feed the machine? I don't think that that > improves > life for anybody, except perhaps for the owners of said LLMs. > > Yours, > Laurenz Albe >
Re: Feature request: Add a llms.txt file to the docs for AIs to learn
The convention here is to add responses inline, after the quoted content being responded to. On Sunday, November 2, 2025, Adrián Cuadrado Chavarría < [email protected]> wrote: > > Why should we invest effort to feed the machine? > > Great news: you don't have to. I don't mind investing the effort myself so > no one else has to. It's just a matter of creating a script that would > concatenate all markdown files of the documentation and run it > automatically whenever a change is made in any document. > The current build for the documentation doesn’t produce Markdown. > > > I don't think that that improves life for anybody, except perhaps for > the owners of said LLMs. > > Users of LLMs would appreciate having a feature like this one. > People are going to use LLMs - I have no problem with my volunteer efforts to improve the documentation to be read and referenced by LLMs so that they at least have correct content to work from and save me the effort of having to further correct mistakes or deal with misinformed people. Not that I’m volunteering to do the work. It LLMs seem like a natural pairing with open source principles. Our documentation is already known to be an official source for attribution purposes. Though I’m not totally convinced about it ability to handle our versioning policies correctly if we rely on generalized models scraping us. David J.
Re: SQL command : ALTER DATABASE OWNER TO
ne 2. 11. 2025 v 18:23 odesílatel Laurenz Albe napsal: > > On Wed, 2024-01-24 at 15:26 +0100, Daniel Gustafsson wrote: > > > On 24 Jan 2024, at 15:23, Laurenz Albe wrote: > > > > > > On Wed, 2024-01-24 at 11:08 +0100, [email protected] wrote: > > > > for this "ALTER DATABASE" form, it should be mentioned that after > > > > execution of the command, > > > > the old database owner loses all his privileges on it (even connection) > > > > although it might > > > > still owns schemas or objects (tables, index,...) inside it. > > > > > > > > Thanks in advance to add this important precision. > > > > > > How about this: > > > > > > diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml > > > index 4044f0908f..44042f863c 100644 > > > --- a/doc/src/sgml/ddl.sgml > > > +++ b/doc/src/sgml/ddl.sgml > > > @@ -1891,6 +1891,8 @@ ALTER TABLE table_name > > > OWNER TO new_owne > > >Superusers can always do this; ordinary roles can only do it if they > > > are > > >both the current owner of the object (or inherit the privileges of the > > >owning role) and able to SET ROLE to the new owning > > > role. > > > + All object privileges of the old owner are transferred to the new > > > owner > > > + along with the ownership. > > > > > > > Doesn't seem unreasonable to me, it won't make the docs harder to read and > > use > > for experienced users while it may make them easier to follow for new users. > > Here is a patch for this change. Did a quick test: during review retro=# CREATE USER josef; CREATE DATABASE testdb OWNER josef; GRANT ALL ON DATABASE testdb TO josef; CREATE ROLE CREATE DATABASE GRANT retro=# \l testdb List of databases Name | Owner | Encoding | Locale Provider | Collate |Ctype | ICU Locale | ICU Rules | Access privileges +---+--+-+-+-++---+--- testdb | josef | UTF8 | libc| cs_CZ.UTF-8 | cs_CZ.UTF-8 || | =Tc/josef+ | | | | | || | josef=CTc/josef (1 row) retro=# ALTER DATABASE testdb OWNER TO retro; ALTER DATABASE retro=# \l testdb List of databases Name | Owner | Encoding | Locale Provider | Collate |Ctype | ICU Locale | ICU Rules | Access privileges +---+--+-+-+-++---+--- testdb | retro | UTF8 | libc| cs_CZ.UTF-8 | cs_CZ.UTF-8 || | =Tc/retro+ | | | | | || | retro=CTc/retro (1 row) It works exactly as described in this patch. +1 > Yours, > Laurenz Albe
