Re: ON CONFLICT issues around whole row vars,

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: ON CONFLICT issues around whole row vars,
Дата
Msg-id 20151001231748.GZ32326@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: ON CONFLICT issues around whole row vars,  (Peter Geoghegan <pg@heroku.com>)
Ответы Re: ON CONFLICT issues around whole row vars,
Список pgsql-hackers
On 2015-10-01 16:13:12 -0700, Peter Geoghegan wrote:
> However, we're checking the excluded tuple (the might-be-inserted,
> might-be-excluded tuple that reflects before row insert trigger
> effects) with WCO_RLS_INSERT_CHECK, not WCO_RLS_UPDATE_CHECK. The
> WCO_RLS_UPDATE_CHECK applies to the tuple to be appended to the
> relation (the tuple that an UPDATE makes supersede some existing
> tuple, a new row version).

You can already see the effects of an INSERT modified by before triggers
via RETURNING. No?

Greetings,

Andres Freund



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: ON CONFLICT issues around whole row vars,
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pg_dump LOCK TABLE ONLY question