Re: Final spec on per-database/per-user settings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Final spec on per-database/per-user settings
Date
Msg-id 23913.1014955037@sss.pgh.pa.us
Whole thread Raw
In response to Final spec on per-database/per-user settings  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: More general configurability of session startup actions
Next
From: Bruce Momjian
Date:
Subject: Re: elog() patch