Re: Documentation for initdb option --waldir

2025-04-05 Thread David G. Johnston
On Wed, Mar 26, 2025 at 2:35 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/app-initdb.html > Description: > > Hi all, > > During troubleshooting with a customer we found that it might help to know

Re: Documentation for initdb option --waldir

2025-03-29 Thread David G. Johnston
On Saturday, March 29, 2025, Robert Treat wrote: > On Thu, Mar 27, 2025 at 5:57 PM David G. Johnston > wrote: > > On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: > >> On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston > >> wrote: > >> > I expanded upon the material regarding using differen

Re: Documentation for initdb option --waldir

2025-03-29 Thread Laurenz Albe
On Sat, 2025-03-29 at 10:26 -0400, Robert Treat wrote: > "Best practice is to create a directory within the mount-point > directory that is owned by the PostgreSQL user, and then create the > data directory within that. This avoids permissions problems,..." > > Which I do remember having tried to

Re: Documentation for initdb option --waldir

2025-03-29 Thread David G. Johnston
On Saturday, March 29, 2025, Gurjeet Singh wrote: > On Sat Mar 29, 2025 at 9:26 AM PDT, Laurenz Albe wrote: > > > On the other hand, PostgreSQL will protest if the directory isn't > > empty... > > Specifically, initdb will complain if the directory it's trying to > initialize is not empty. > For

Re: Documentation for initdb option --waldir

2025-03-29 Thread Gurjeet Singh
On Sat Mar 29, 2025 at 9:26 AM PDT, Laurenz Albe wrote: > On the other hand, PostgreSQL will protest if the directory isn't > empty... Specifically, initdb will complain if the directory it's trying to initialize is not empty. Best regards, Gurjeet http://Gurje.et

Re: Documentation for initdb option --waldir

2025-03-29 Thread Gurjeet Singh
On Sat Mar 29, 2025 at 7:26 AM PDT, Robert Treat wrote: > On Thu, Mar 27, 2025 at 5:57 PM David G. Johnston > wrote: >> On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: >>> On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston >>> wrote: >>> > I expanded upon the material regarding using differe

Re: Documentation for initdb option --waldir

2025-03-29 Thread Robert Treat
On Sat, Mar 29, 2025 at 10:58 AM David G. Johnston wrote: > > On Saturday, March 29, 2025, Robert Treat wrote: >> >> On Thu, Mar 27, 2025 at 5:57 PM David G. Johnston >> wrote: >> > On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: >> >> On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston >> >

Re: Documentation for initdb option --waldir

2025-03-29 Thread Robert Treat
On Thu, Mar 27, 2025 at 5:57 PM David G. Johnston wrote: > On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: >> On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston >> wrote: >> > I expanded upon the material regarding using different file systems and >> > disks. >> > >> > I would like to add a

Re: Documentation for initdb option --waldir

2025-03-27 Thread David G. Johnston
On Thu, Mar 27, 2025 at 2:28 PM Robert Treat wrote: > On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston > wrote: > > > > Version 2 Attached > > > > -This option specifies the directory where the write-ahead log > > -should be stored. > > +This option specifies the direct

Re: Documentation for initdb option --waldir

2025-03-27 Thread Robert Treat
On Thu, Mar 27, 2025 at 12:06 PM David G. Johnston wrote: > > Version 2 Attached > > -This option specifies the directory where the write-ahead log > -should be stored. > +This option specifies the directory in which to store write-ahead > log files. > +See for mo

Re: Documentation for initdb option --waldir

2025-03-27 Thread David G. Johnston
Version 2 Attached There being two places now (plus doing it manually) I decided to write this material in the WAL chapter as opposed to application-specific Notes. A new section seemed warranted. I expanded upon the material regarding using different file systems and disks. I would like to add

Re: Documentation for initdb option --waldir

2025-03-27 Thread Euler Taveira
On Thu, Mar 27, 2025, at 8:40 AM, Theodor Herlo wrote: > Both look great to me! I thought the advantage of having different devices > is also to easy I/O load. But I guess you have to decide for yourself what is > the best strategy. For me it was important to know what initdb does with > ---wal

AW: Documentation for initdb option --waldir

2025-03-27 Thread Theodor Herlo
prüngliche Nachricht- Von: Laurenz Albe Gesendet: Donnerstag, 27. März 2025 11:32 An: David G. Johnston ; Theodor Herlo ; pgsql-docs@lists.postgresql.org Betreff: Re: Documentation for initdb option --waldir [Sie erhalten nicht häufig E-Mails von laurenz.a...@cybertec.at. Weitere Informationen

Re: Documentation for initdb option --waldir

2025-03-27 Thread Laurenz Albe
On Wed, 2025-03-26 at 17:34 -0700, David G. Johnston wrote: > + > + The pg_wal subdirectory will always exist within the > + data directory. This is where PostgreSQL > + sends its write-ahead log (WAL) files. > + Specifying the --waldir option turns this subdirectory > entry > + into

Documentation for initdb option --waldir

2025-03-26 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/app-initdb.html Description: Hi all, During troubleshooting with a customer we found that it might help to know that initdb will create a symbolic link from data/pg_wal to the custom dire