Re: Another way to fix inherited UPDATE/DELETE

Поиск
Список
Период
Сортировка
От Etsuro Fujita
Тема Re: Another way to fix inherited UPDATE/DELETE
Дата
Msg-id 5C6D3102.6000904@lab.ntt.co.jp
обсуждение исходный текст
Ответ на Another way to fix inherited UPDATE/DELETE  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Another way to fix inherited UPDATE/DELETE  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
(2019/02/20 6:48), Tom Lane wrote:
> In the case of a standard inheritance or partition tree, this seems to
> go through really easily, since all the children could share the same
> returned CTID column (I guess you'd also need a TABLEOID column so you
> could figure out which table to direct the update back into).  It gets
> a bit harder if the tree contains some foreign tables, because they might
> have different concepts of row identity, but I'd think in most cases you
> could still combine those into a small number of output columns.

If this is the direction we go in, we should work on the row ID issue 
[1] before this?

Best regards,
Etsuro Fujita

[1] https://www.postgresql.org/message-id/1590.1542393315%40sss.pgh.pa.us



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

Предыдущее
От: "Matsumura, Ryo"
Дата:
Сообщение: RE: SQL statement PREPARE does not work in ECPG
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: restrict pg_stat_ssl to superuser?