| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: AW: Unhappy thoughts about pg_dump and objects inherite d from template1 |
| Date: | 2000-11-09 15:19:53 |
| Message-ID: | 6267.973783193@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
>> in fact template0 needn't be a real database at all, just a
>> $PGDATA/base subdirectory with no pg_database entry.
> I like this "not really a database" idea.
> Might even be something for $libdir, no ?
I thought about that but concluded that it'd just be a way to shoot
ourselves in the foot. The postmaster and backend per se don't know
where $PGLIB is (offhand, I think only the initdb and createlang
scripts do). If we add a dependency on $PGLIB, I think we'll just
be setting up a new way to cause configuration mistakes --- and copying
the wrong template0 data would be a pretty messy sort of mistake. So
keeping the template data under $PGDATA seems like the way to go.
However, template0 needn't necessarily be under $PGDATA/base, it could
be its own subdirectory of $PGDATA. I'm not sure if that's a better
arrangement or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pete.forman | 2000-11-09 15:28:13 | Re: problems with configure |
| Previous Message | Martin A. Marques | 2000-11-09 15:04:54 | Re: problems with configure |