Re: Copy-pasto in the ExecForeignDelete documentation
От | Robert Haas |
---|---|
Тема | Re: Copy-pasto in the ExecForeignDelete documentation |
Дата | |
Msg-id | CA+TgmoaZGoxVX2w627CK9OSLi88_7HdU3nNncAcqA0mCkt+5wA@mail.gmail.com обсуждение исходный текст |
Ответ на | Copy-pasto in the ExecForeignDelete documentation (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>) |
Ответы |
Re: Copy-pasto in the ExecForeignDelete documentation
|
Список | pgsql-hackers |
On Mon, Feb 1, 2016 at 5:26 AM, Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> wrote: > I don't think the data is referenced by the AFTER ROW DELETE triggers. Why do you think that? And why would DELETE triggers be different from UPDATE triggers, which do something similar? I looked up the history of this code and it was introduced in 7cbe57c3, which added support for triggers on foreign tables. Noah did that commit and he's rarely wrong about stuff like this, so I suspect you may be missing something. One thing to consider is whether the version of the row that finally gets deleted is necessarily the same as the version originally selected from the remote side; e.g. suppose the remote side has triggers, too. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: