| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
| Cc: | Greg Copeland <greg(at)CopelandConsulting(dot)Net>, Curt Sampson <cjs(at)cynic(dot)net>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WAL file location |
| Date: | 2002-08-03 01:12:39 |
| Message-ID: | 200208030112.g731Cdo08185@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart wrote:
> > > I am wondering why we even want to specify the WAL location anywhere
> > > except as a flag to initdb. If you specify a location at initdb time,
> > > it creates the /xlog directory, then symlinks it into /data.
> > Does this have any negative implications for Win32 ports?
>
> Sure. the symlinks thing was just a suggestion. Everything else is
> portable for sure... Or is there some other area you are concerned
> about?
I was just wondering why we would deal with environment variables or
postgresql.conf settings. Just make it an initdb flag, create it in the
desired location with a symlink in /data and then we don't have to do
any more work for WAL locations unless people want to move it around
after then initdb'ed, in which case they have to do it manually.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2002-08-03 01:15:03 | Re: Planned simplification of catalog index updates |
| Previous Message | Mikheev, Vadim | 2002-08-03 01:07:40 | Re: PITR, checkpoint, and local relations |