Re: When and where to check for function permissions
От | Peter Eisentraut |
---|---|
Тема | Re: When and where to check for function permissions |
Дата | |
Msg-id | Pine.LNX.4.30.0202131922250.683-100000@peter.localdomain обсуждение исходный текст |
Ответ на | Re: When and where to check for function permissions (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: When and where to check for function permissions
|
Список | pgsql-hackers |
Tom Lane writes: > Peter Eisentraut <peter_e@gmx.net> writes: > > Now I remembered the way SQL99 specifies > > function resolution, which has the permission check before the function > > resolution begins. > > That may be what the spec says, but I think the spec is completely > brain-dead in this regard and should be ignored. Why? > We do not resolve table names that way, why should we resolve function > names? We do not resolve table names at all. > Even more to the point, what happens when someone adds or revokes > privileges that would affect already-planned queries? The query plans are invalidated. Note: I'm not convinced of this idea either. But proclaiming it brain-dead isn't going to push me either way. You could say Unix shells are brain-dead, too, because they do the same thing. -- Peter Eisentraut peter_e@gmx.net
В списке pgsql-hackers по дате отправления: