Re: initdb username doc bug

2024-01-10 Thread Bruce Momjian
On Wed, Jan 10, 2024 at 06:05:17PM +0100, Álvaro Herrera wrote: > On 2024-Jan-10, Bruce Momjian wrote: > > > On Mon, Jan 8, 2024 at 04:50:19PM -0500, Tom Lane wrote: > > > Bruce Momjian writes: > > > > Agreed, updated patch attached. > > > > > > WFM. > > > > Patch applied back to PG 16, which

Re: initdb username doc bug

2024-01-10 Thread Álvaro Herrera
On 2024-Jan-10, Bruce Momjian wrote: > On Mon, Jan 8, 2024 at 04:50:19PM -0500, Tom Lane wrote: > > Bruce Momjian writes: > > > Agreed, updated patch attached. > > > > WFM. > > Patch applied back to PG 16, which is where the erroneous text was > added. Thank you! It looks good to me too. So

Re: initdb username doc bug

2024-01-10 Thread Bruce Momjian
On Mon, Jan 8, 2024 at 04:50:19PM -0500, Tom Lane wrote: > Bruce Momjian writes: > > Agreed, updated patch attached. > > WFM. Patch applied back to PG 16, which is where the erroneous text was added. -- Bruce Momjian https://momjian.us EDB htt

Re: initdb username doc bug

2024-01-08 Thread Tom Lane
Bruce Momjian writes: > Agreed, updated patch attached. WFM. regards, tom lane

Re: initdb username doc bug

2024-01-08 Thread David G. Johnston
On Mon, Jan 8, 2024 at 2:26 PM Bruce Momjian wrote: > On Sat, Jan 6, 2024 at 11:27:14PM -0500, Tom Lane wrote: > > "David G. Johnston" writes: > > > Or just the bit more verbose “user running the initdb command” and > don’t > > > bother giving it a label, which is basically the approach used in

Re: initdb username doc bug

2024-01-08 Thread Bruce Momjian
On Sat, Jan 6, 2024 at 11:27:14PM -0500, Tom Lane wrote: > "David G. Johnston" writes: > > Or just the bit more verbose “user running the initdb command” and don’t > > bother giving it a label, which is basically the approach used in the > > description for initdb anyway. > > Or if you want a fe

Re: initdb username doc bug

2024-01-06 Thread Tom Lane
"David G. Johnston" writes: > Or just the bit more verbose “user running the initdb command” and don’t > bother giving it a label, which is basically the approach used in the > description for initdb anyway. Or if you want a few more words, "name of the operating-system user running initdb". I d

Re: initdb username doc bug

2024-01-06 Thread David G. Johnston
On Saturday, January 6, 2024, David G. Johnston wrote: > On Saturday, January 6, 2024, Bruce Momjian wrote: > >> >> geteuid() returns the effective user ID of the calling process. >> >> so it is not the owner of the data dirctory, but the installation user. >> >> I am open to saying that

Re: initdb username doc bug

2024-01-06 Thread David G. Johnston
On Saturday, January 6, 2024, Bruce Momjian wrote: > On Sat, Jan 6, 2024 at 08:11:14PM -0700, David G. Johnston wrote: > > On Saturday, January 6, 2024, Bruce Momjian wrote: > > > > This commit: > > > > commit 910cab820d > > Author: Alvaro Herrera > > Da

Re: initdb username doc bug

2024-01-06 Thread Bruce Momjian
On Sat, Jan 6, 2024 at 08:11:14PM -0700, David G. Johnston wrote: > On Saturday, January 6, 2024, Bruce Momjian wrote: > > This commit: > >         commit 910cab820d >         Author: Alvaro Herrera >         Date:   Fri Nov 18 11:59:26 2022 +0100 > >             Add gloss

Re: initdb username doc bug

2024-01-06 Thread David G. Johnston
On Saturday, January 6, 2024, Bruce Momjian wrote: > This commit: > > commit 910cab820d > Author: Alvaro Herrera > Date: Fri Nov 18 11:59:26 2022 +0100 > > Add glossary entries related to superusers > > Extracted from a more ambitious patch. > >

initdb username doc bug

2024-01-06 Thread Bruce Momjian
This commit: commit 910cab820d Author: Alvaro Herrera Date: Fri Nov 18 11:59:26 2022 +0100 Add glossary entries related to superusers Extracted from a more ambitious patch. Author: David G. Johnston