Per-database and per-user GUC settings
От | Peter Eisentraut |
---|---|
Тема | Per-database and per-user GUC settings |
Дата | |
Msg-id | Pine.LNX.4.30.0201281607420.688-100000@peter.localdomain обсуждение исходный текст |
Ответы |
Re: Per-database and per-user GUC settings
|
Список | pgsql-hackers |
As hinted somewhere within the schema-objects thread, I'm implementing GUC settings that are stored in the pg_shadow and pg_database system catalogs and are activated in sessions for that user or database. The basic functionality is done, although two issues sort of need a show of hands. First, the order in which these settings are processed: I figured user should be last. I've also got these settings for each group, but this would mean that if a user is a member of more than one group he gets a rather random processing order. Any comments on that? If the group thing stays, I think the most reasonable processing order is database, groups, user, since it would be weird to have database between groups and user. Second, we need a few commands to set these things. My first thought was SET {USER name | DATABASE name} [SESSION] DEFAULT varname TO value; but it would also make sense to have ALTER {USER name | DATABASE name} SET DEFAULT varname TO value; Or there could be other permutations that are more or less wordy. Suggestions? Perhaps a reference to another RDBMS can give a hint. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: