| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "David Fetter" <david(at)fetter(dot)org> |
| Cc: | "Joshua Drake" <jd(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: initdb change |
| Date: | 2008-08-25 16:54:00 |
| Message-ID: | 48B2E3A8.9070500@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Fetter wrote:
> There's already a way to specify where xlogs should be via
> -X/--xlogdir. What that doesn't do is put the xlogdir where a DBA
> would naturally expect to find it. When that DBA doesn't find it in
> the place they expect, very bad knock-on decisions are likely to
> result.
I don't understand what that natural place is that you refer to, and it
seems that others don't either. Could you walk us through how one would
use the new option?
mount something somewhere
???
initdb -D /mnt/data -X ???
postgres -D /mnt/data
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Drake | 2008-08-25 16:54:26 | Re: initdb change |
| Previous Message | David Fetter | 2008-08-25 16:42:21 | Re: initdb change |