| 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>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Fernando Nasser <fnasser(at)redhat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RFD: schemas and different kinds of Postgres objects |
| Date: | 2002-01-25 04:33:52 |
| Message-ID: | 200201250433.g0P4XqD10470@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut wrote:
> Tom Lane writes:
>
> > It'd be nice though if
> > the behavior could be changed after connection by a SET statement, which
> > would be lots easier if the setting were GUC-controlled. Peter, you see
> > any way to resolve that?
>
> We had a text[] field to pg_shadow and/or pg_database containing
> name=value assignments which are executed just before the session starts.
> Doesn't look terribly difficult, and it's something I've always wanted to
> do anyway.
So are thinking of "dbname=schema_type"? Seems this is really something
that should be in pg_database. If you create a database, who wants to
edit postgresql.conf to set its default schema type? Why not set the
GUC value from pg_database?
--
Bruce Momjian | http://candle.pha.pa.us
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 | Jan Wieck | 2002-01-25 04:35:15 | Re: PostgreSQL crashes with Qmail-SQL |
| Previous Message | Gavin Sherry | 2002-01-25 04:25:05 | Re: RFD: schemas and different kinds of Postgres objects |