Seeming contradiction in 22.1
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/15/database-roles.html Description: In chapter 22.1 the following text seems to imply the role will have "the same name as the user that initialised" it and also the "role will be named postgres". Which cannot both be true, or perhaps the text is trying to say something else, but in doing so is not clear. "This role is always a “superuser”, and by default (unless altered when running initdb) it will have the same name as the operating system user that initialized the database cluster. Customarily, this role will be named postgres. "
Re: Seeming contradiction in 22.1
On Monday, March 20, 2023, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/database-roles.html > Description: > > In chapter 22.1 the following text seems to imply the role will have "the > same name as the user that initialised" it and also the "role will be named > postgres". Which cannot both be true, or perhaps the text is trying to say > something else, but in doing so is not clear. > > "This role is always a “superuser”, and by default (unless altered when > running initdb) it will have the same name as the operating system user > that > initialized the database cluster. Customarily, this role will be named > postgres. " > The words “default” and “unless altered” seem quite clear to me. In particular, the “customarily” part is accomplished usually by creating an operating system user named postgres and then running initdb as that user. David J.
Re: Seeming contradiction in 22.1
On Wed, Mar 22, 2023 at 3:41 PM maja zaloznik wrote: > My issue is that - at least as far as i can recall - the default superuser > was already named postgres > There is no compiled-in default for the name of the bootstrap superuser. It is chosen during initdb using the algorithm described (i.e., o/s user running initdb or the name specified on the CLI) David J.
Publishing Postgres Manual as a book
Hello, The Postgres Manual is available online as a PDF but I think having it in a book form could be useful to some. Is it legal for me to publish the manual as a book? I cannot find any email address on PostgreSQL website to ask such questions. This is the closest mailing list I could find. S.
Re: Publishing Postgres Manual as a book
> On 23/03/2023 02:35 CET Siddharth Jain wrote: > > The Postgres Manual is available online as a PDF but I think having it in a > book form could be useful to some. > > Is it legal for me to publish the manual as a book? IANAL, but I'd say yes as long as you don't take a fee. The legal notice of the documentation grants distribution of the documentation "for any purpose, without fee". [0] Also mind the trademark policy. [1] [0] https://www.postgresql.org/docs/current/legalnotice.html [1] https://www.postgresql.org/about/policies/trademarks/ -- Erik
Re: Publishing Postgres Manual as a book
2023年3月23日(木) 12:23 Erik Wienhold : > > > On 23/03/2023 02:35 CET Siddharth Jain wrote: > > > > The Postgres Manual is available online as a PDF but I think having it in a > > book form could be useful to some. > > > > Is it legal for me to publish the manual as a book? > > IANAL, but I'd say yes as long as you don't take a fee. The legal notice of > the documentation grants distribution of the documentation "for any purpose, > without fee". Also not a lawyer, but the full sentence is: > Permission to use, copy, modify, and distribute this software and its > documentation for any purpose, without fee, and without a written agreement is > hereby granted which in my non-lawyerly interpretation means anyone copying, modifying and distributing the documentation may do so without paying a fee. A distributor could charge what they like. AFAIR the documentation has previously been published in book form, though as it runs to about 3,000 A4 pages now, the logistics are non-trivial. Regards Ian Barwick
Re: Publishing Postgres Manual as a book
2023年3月23日(木) 12:34 Ian Lawrence Barwick : > > 2023年3月23日(木) 12:23 Erik Wienhold : > > > > > On 23/03/2023 02:35 CET Siddharth Jain wrote: > > > > > > The Postgres Manual is available online as a PDF but I think having it in > > > a > > > book form could be useful to some. > > > > > > Is it legal for me to publish the manual as a book? > > > > IANAL, but I'd say yes as long as you don't take a fee. The legal notice of > > the documentation grants distribution of the documentation "for any purpose, > > without fee". > > Also not a lawyer, but the full sentence is: > > > Permission to use, copy, modify, and distribute this software and its > > documentation for any purpose, without fee, and without a written agreement > > is > > hereby granted > > which in my non-lawyerly interpretation means anyone copying, modifying and > distributing the documentation may do so without paying a fee. A distributor > could charge what they like. AFAIR the documentation has previously been > published in book form e.g.: https://www.amazon.com/PostgreSQL-9-0-Official-Documentation-Language/dp/1596822465 > though as it runs to about 3,000 A4 pages now, the logistics are non-trivial. The PostgreSQL 15 A4 PDF has 2854 pages. Regards Ian Barwick
Re: Publishing Postgres Manual as a book
> On 23/03/2023 04:34 CET Ian Lawrence Barwick wrote: > > 2023年3月23日(木) 12:23 Erik Wienhold : > > > > > On 23/03/2023 02:35 CET Siddharth Jain wrote: > > > > > > The Postgres Manual is available online as a PDF but I think having it in > > > a > > > book form could be useful to some. > > > > > > Is it legal for me to publish the manual as a book? > > > > IANAL, but I'd say yes as long as you don't take a fee. The legal notice of > > the documentation grants distribution of the documentation "for any purpose, > > without fee". > > Also not a lawyer, but the full sentence is: > > > Permission to use, copy, modify, and distribute this software and its > > documentation for any purpose, without fee, and without a written agreement > > is > > hereby granted > > which in my non-lawyerly interpretation means anyone copying, modifying and > distributing the documentation may do so without paying a fee. A distributor > could charge what they like. I know the fee clause from licenses such as Zero-Clause BSD, ISC License, and GPLv3. They state "with or without fee" or "gratis or for a fee" pertaining to the distribution. That's also how I interpret the fee clause in the PostgreSQL license with the difference that it does not permit taking a fee. > AFAIR the documentation has previously been published in book form, though as > it runs to about 3,000 A4 pages now, the logistics are non-trivial. It's also out of date pretty quickly with four releases a year. -- Erik
Re: Publishing Postgres Manual as a book
Erik Wienhold writes: > On 23/03/2023 04:34 CET Ian Lawrence Barwick wrote: >> Also not a lawyer, but the full sentence is: >>> Permission to use, copy, modify, and distribute this software and its >>> documentation for any purpose, without fee, and without a written agreement >>> is >>> hereby granted >> which in my non-lawyerly interpretation means anyone copying, modifying and >> distributing the documentation may do so without paying a fee. A distributor >> could charge what they like. > I know the fee clause from licenses such as Zero-Clause BSD, ISC License, and > GPLv3. They state "with or without fee" or "gratis or for a fee" pertaining > to > the distribution. That's also how I interpret the fee clause in the > PostgreSQL > license with the difference that it does not permit taking a fee. No, I agree with Ian: our license says that the Postgres project does not require a fee. It does not say that someone redistributing the material can't charge for their efforts. It would obviously be ridiculous to expect someone to print a multi-thousand-page book and then give it away for free. I do question the practicality and environmental cost of putting such short-lived material on dead trees, though ... regards, tom lane
