| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Final spec on per-database/per-user settings |
| Date: | 2002-03-01 03:57:17 |
| Message-ID: | 23913.1014955037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Here is what I have implemented for database and user-specific run-time
> configuration settings. Unless there are desired changes, I plan to check
> this in tomorrow.
Semantics seem fine, but an implementation detail:
> (The truth is, these settings are processed somewhere in the middle of
> InitPostgres(). This way we only have to read pg_shadow and pg_database
> once per session startup. This keeps the performance impact negligible.)
I trust the pg_database row is read during ReverifyMyDatabase, and isn't
the one fetched by GetRawDatabaseInfo...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-03-01 05:00:23 | Re: elog() patch |
| Previous Message | Peter Eisentraut | 2002-03-01 02:08:28 | More general configurability of session startup actions |