| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: config files in /data |
| Date: | 2000-05-31 19:43:10 |
| Message-ID: | 200005311943.PAA23298@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ Charset ISO-8859-1 unsupported, converting... ]
> Tom Lane writes:
>
> > Rather than restricting database names, we should keep these files in
> > a different subdirectory. I agree that it's a good idea to separate
> > them from the directly-editable config files, just not to put them in
> > data/base/ ...
>
> Right. How about `$PGDATA/internal'? Can't be more obvious. Perhaps with
> that we could also have initdb clean up a little more respectfully.
Are we talking about moveing pg_log and pg_shadow? Maybe call it
/global because the tables are global to all databases.
--
Bruce Momjian | http://www.op.net/~candle
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 | Jeff Hoffmann | 2000-05-31 19:47:37 | bug or feature? (regarding rules) |
| Previous Message | Peter Eisentraut | 2000-05-31 19:34:44 | Re: config files in /data |