Re: copy.c handling for RLS is insecure

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: copy.c handling for RLS is insecure
Дата
Msg-id 20150709084148.GU10242@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: copy.c handling for RLS is insecure  (Noah Misch <noah@leadboat.com>)
Ответы Re: copy.c handling for RLS is insecure  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
Дерево обсуждения 
On 2015-07-09 01:28:28 -0400, Noah Misch wrote:
> > - Keep the OID check, shouldn't hurt to have it
> 
> What benefit is left?

A bit of defense in depth. We execute user defined code in COPY
(e.g. BEFORE triggers). That user defined code could very well replace
the relation. Now I think right now that'd happen late enough, so the
second lookup already happened. But a bit more robust defense against
that sounds good to me.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: Further issues with jsonb semantics, documentation
Следующее
От: David Rowley
Дата:
Сообщение: Re: Sharing aggregate states between different aggregate functions