| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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 02:28:34 |
| Message-ID: | 3D4B3FD2.AF6A42AA@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
...
> 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.
Well, I have the same reaction to symlinks as some others might have to
environment variables ;) Symlinks are inherently evil for determining
fundamental properties of our database, and inherently evil for
determining locations of files within our database.
They don't scale, they are not portable, and it is difficult for
applications (like the Postgres backend) to know that they are dealing
with a simlink or a real file.
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-08-03 02:36:05 | Re: WAL file location |
| Previous Message | Bruce Momjian | 2002-08-03 01:46:28 | Re: Planned simplification of catalog index updates |