| From: | Bill Studenmund <wrstuden(at)netbsd(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Fernando Nasser <fnasser(at)redhat(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFD: schemas and different kinds of Postgres objects |
| Date: | 2002-01-25 22:07:58 |
| Message-ID: | Pine.NEB.4.33.0201251358390.12100-100000@vespasia.home-net.internetconnect.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 24 Jan 2002, Bruce Momjian wrote:
> I think we could set the database default at db creation time, then
> allow SET to modify that default per session; seems flexible enough.
> It is basically a GUC value who's default is stored in pg_database
> rather than postgresql.conf. You could use postgresql.conf to set the
> default schema type at db creation time.
Specifically to the question of schema pathing, why would you want it to
be session-settable? Either your DB app is designed to work w/ schemas, or
it isn't. That's a pretty fundamental design concept. Given that, I don't
see how it can make sense to try to operate in the opposite mode as the
app was designed for - that'll only lead to chaos.
Take care,
Bill
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-25 22:26:14 | Re: RFD: schemas and different kinds of Postgres objects |
| Previous Message | Tom Lane | 2002-01-25 22:05:46 | Re: sequence indexes |