Re: initdb username doc bug

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

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

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

Bruce Momjian writes: > Agreed, updated patch attached. WFM. regards, tom lane

Re: initdb username doc bug

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

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

"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

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

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

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

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. > >

Re: initdb: nothing about template0

PG Doc comments form writes: > Is it correct that this page does not contain information about the > template0 database. > The same goes for the "Create Database Cluster" page > (https://www.postgresql.org/docs/14/creating-cluster.html). Yeah, this text evidently wasn't updated when we invented t

Re: initdb - creating clusters

Daniel Gustafsson writes: >> On 2 Sep 2020, at 18:43, Tom Lane wrote: >> I took a stab at doing it that way, as attached. (I couldn't resist >> the temptation to do some minor editing on adjacent material, too.) > LGTM. I didn't try to build the docs with this applied, but reading it I > can'

Re: initdb - creating clusters

> On 2 Sep 2020, at 18:43, Tom Lane wrote: > I took a stab at doing it that way, as attached. (I couldn't resist > the temptation to do some minor editing on adjacent material, too.) LGTM. I didn't try to build the docs with this applied, but reading it I can't see anything odd about the marku

Re: initdb - creating clusters

Daniel Gustafsson writes: > On 30 Aug 2020, at 17:21, Tom Lane wrote: >> Do you have a feeling one way or the other about whether to repeat >> some of this text in each of the relevant sub-sections? I initially >> didn't want to do that, but thinking about how people consume the >> HTML docs, I'

Re: initdb - creating clusters

> On 30 Aug 2020, at 17:21, Tom Lane wrote: > > Thomas Munro writes: >> + The discussions in this chapter assume that you are working with >> + an unmodified version of PostgreSQL, >> + for example one that you built from source according to the directions >> + in the preceding chapters. If

Re: initdb - creating clusters

On 30.08.20 17:21, Tom Lane wrote: Do you have a feeling one way or the other about whether to repeat some of this text in each of the relevant sub-sections? I initially didn't want to do that, but thinking about how people consume the HTML docs, I'm afraid that anything not appearing on the sam

Re: initdb - creating clusters

Thomas Munro writes: > + The discussions in this chapter assume that you are working with > + an unmodified version of PostgreSQL, > + for example one that you built from source according to the directions > + in the preceding chapters. If you are working with a pre-packaged > Rather than "u

Re: initdb - creating clusters

On Wed, Aug 26, 2020 at 12:05 AM Daniel Gustafsson wrote: > I took the liberty of adding the proposed patch upthread to the next > commitfest > to make sure it's not forgotten about, as I do think it will improve the docs. + The discussions in this chapter assume that you are working with + an

Re: initdb - creating clusters

> On 22 Jul 2020, at 18:34, Bruce Momjian wrote: > > On Tue, Jul 21, 2020 at 10:40:59AM +0200, Daniel Gustafsson wrote: >>> On 21 Jul 2020, at 02:25, Bruce Momjian wrote: >>> >>> On Thu, Jul 9, 2020 at 03:25:14PM +, PG Doc comments form wrote: looking. For instance the documentation

Re: initdb - creating clusters

On Tue, Jul 21, 2020 at 10:40:59AM +0200, Daniel Gustafsson wrote: > > On 21 Jul 2020, at 02:25, Bruce Momjian wrote: > > > > On Thu, Jul 9, 2020 at 03:25:14PM +, PG Doc comments form wrote: > >> looking. For instance the documentation on replication strategies includes > >> proprietary sol

Re: initdb - creating clusters

> On 21 Jul 2020, at 02:25, Bruce Momjian wrote: > > On Thu, Jul 9, 2020 at 03:25:14PM +, PG Doc comments form wrote: >> looking. For instance the documentation on replication strategies includes >> proprietary solutions. > > Uh, what proprietary solutions are listed in our documentation?

Re: initdb - creating clusters

On Thu, Jul 9, 2020 at 03:25:14PM +, PG Doc comments form wrote: > looking. For instance the documentation on replication strategies includes > proprietary solutions. Uh, what proprietary solutions are listed in our documentation? -- Bruce Momjian https://momjian.us Enterprise

Re: initdb - creating clusters

> On 12 Jul 2020, at 00:24, Tom Lane wrote: > > Daniel Gustafsson writes: >>> On 11 Jul 2020, at 23:36, Tom Lane wrote: >>> + For example, there may be special scripts for creating a database >>> + cluster. There almost certainly will be a mechanism for starting >>> + the server, > >> Aren

Re: initdb - creating clusters

On Sat, Jul 11, 2020 at 2:37 PM Tom Lane wrote: > Another approach would be to put something along this line at the heads > of each of the relevant sections, which'd be 18.1, 18.2, 18.3, 18.5, > and 18.6 by my count. That seems very repetitive; but it would have > the advantage that people could

Re: initdb - creating clusters

Daniel Gustafsson writes: >> On 11 Jul 2020, at 23:36, Tom Lane wrote: >> + For example, there may be special scripts for creating a database >> + cluster. There almost certainly will be a mechanism for starting >> + the server, > Aren't we really talking about "running the server as a servi

Re: initdb - creating clusters

> On 11 Jul 2020, at 23:36, Tom Lane wrote: > + For example, there may be special scripts for creating a database > + cluster. There almost certainly will be a mechanism for starting > + the server, Aren't we really talking about "running the server as a service" and not just starting it? P

Re: initdb - creating clusters

Laurenz Albe writes: > On Thu, 2020-07-09 at 15:25 +, PG Doc comments form wrote: >> I would suggest that you include a paragraph stating that various operating >> systems use other commands to avoid version conflict and suggest the reader >> search for ' pg_ctl'. I can understand why you mig

Re: initdb - creating clusters

On Thu, 2020-07-09 at 15:25 +, PG Doc comments form wrote: > I'm searching for what a cluster is and how to create one. The > documentation tells me to use initdb -D path/to/cluster. I am told that > this is installed when I installed postgresql. I try to run it with no > success. Searching

Re: initdb recommendations

On 4/8/19 8:44 AM, Magnus Hagander wrote: > On Mon, Apr 8, 2019 at 2:41 PM Jonathan S. Katz > wrote: > > On 4/8/19 8:25 AM, Peter Eisentraut wrote: > > On 2019-04-05 18:11, Jonathan S. Katz wrote: > >> +    > >> +      We recommend using the -W, >

Re: initdb recommendations

On Mon, Apr 8, 2019 at 2:41 PM Jonathan S. Katz wrote: > On 4/8/19 8:25 AM, Peter Eisentraut wrote: > > On 2019-04-05 18:11, Jonathan S. Katz wrote: > >> + > >> + We recommend using the -W, > --pwprompt, > >> + or --pwfile flags to assign a password to the > database > >> + sup

Re: initdb recommendations

On 4/8/19 8:25 AM, Peter Eisentraut wrote: > On 2019-04-05 18:11, Jonathan S. Katz wrote: >> + >> + We recommend using the -W, >> --pwprompt, >> + or --pwfile flags to assign a password to the >> database >> + superuser, and to override the pg_hba.conf >> default >> + gen

Re: initdb recommendations

On 2019-04-05 18:11, Jonathan S. Katz wrote: > + > + We recommend using the -W, > --pwprompt, > + or --pwfile flags to assign a password to the database > + superuser, and to override the pg_hba.conf default > + generation using -auth-local peer for local > connections, >

Re: initdb recommendations

On Sat, Apr 06, 2019 at 11:35:44AM +0200, Magnus Hagander wrote: > On Fri, Apr 5, 2019 at 10:58 PM Peter Eisentraut > wrote: > > On 2019-04-05 18:11, Jonathan S. Katz wrote: > > > (There could be an additional discussion about whether or not we want to > > > change the default behavior for initdb

Re: initdb recommendations

On Fri, Apr 5, 2019 at 10:58 PM Peter Eisentraut < [email protected]> wrote: > On 2019-04-05 18:11, Jonathan S. Katz wrote: > > (There could be an additional discussion about whether or not we want to > > change the default behavior for initdb, but I would suggest that a safe > > st

Re: initdb recommendations

On 4/5/19 4:58 PM, Peter Eisentraut wrote: > On 2019-04-05 18:11, Jonathan S. Katz wrote: >> (There could be an additional discussion about whether or not we want to >> change the default behavior for initdb, but I would suggest that a safe >> starting point would be to ensure we call this out) >

Re: initdb recommendations

On 2019-04-05 18:11, Jonathan S. Katz wrote: > (There could be an additional discussion about whether or not we want to > change the default behavior for initdb, but I would suggest that a safe > starting point would be to ensure we call this out) I think we should just change the defaults. There

Re: initdb

Hi Tom, I was running initdb command when calling the postgresql96-setup command. Trying to run this as the user postgres failed. /usr/pgsql-9.6/bin/postgresql96-setup initdb The database was created under /var/lib/pgsql/9.6/data thanks Scott. On Mon, Jan 15, 2018 at 4:56 PM, Tom Lane wrot

Re: initdb

=?utf-8?q?PG_Doc_comments_form?= writes: > So I was trying to create a new db with initdb. I tried to run this with > the postgres user after installing the server rpm and it failed with runuser > may not be run as non-root users. So then for fun I tried to run init db > as the root user which