| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, gazzatav(at)gmail(dot)com, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: initdb - creating clusters |
| Date: | 2020-08-29 22:05:50 |
| Message-ID: | CA+hUKGLjvXWn_O1PxAKXFEneGHrOos-QOe3try+ZbqPWrNiNrg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Aug 26, 2020 at 12:05 AM Daniel Gustafsson <daniel(at)yesql(dot)se> 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 unmodified version of <productname>PostgreSQL</productname>,
+ 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 "unmodified", would it be better to say something more
like "without any extra supporting infrastructure"?
My point is that packagers don't typically *modify* PG, rather they
supply a bunch of wrappers (eg Debian postgresql-common), service
management scripting (eg systemd gloopity-gloop), post-install
scripting (eg Debian's policy of automatically starting any service
when you install it, implying that it must also run initdb for you).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-30 15:21:36 | Re: initdb - creating clusters |
| Previous Message | Daniel Gustafsson | 2020-08-28 19:40:59 | Installation on Cygwin |