Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
От | Tom Lane |
---|---|
Тема | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Дата | |
Msg-id | 25791.1059607777@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? (Sean Chittenden <sean@chittenden.org>) |
Ответы |
Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Список | pgsql-patches |
Sean Chittenden <sean@chittenden.org> writes: >> I'm not objecting to the idea of being able to make users read-only. >> I'm objecting to using GUC for it. Send in a patch that, say, adds >> a bool column to pg_shadow, and I'll be happy. > How is that any different than ALTER USER [username] SET > jail_read_only_transactions TO true? It sets something in > pg_shadow.useconfig column, which is permanent. But it has to go through a mechanism that is designed and built to allow that value to be overridden from other places. I think using GUC for this is just asking for trouble. Even if there is no security hole today, it's very easy to imagine future changes in GUC that would unintentionally create one. regards, tom lane
В списке pgsql-patches по дате отправления: