Hi Horiguchi-san, 2014-02-18 19:29 GMT+09:00 Kyotaro HORIGUCHI <horiguchi.kyot...@lab.ntt.co.jp>: > Could you guess any use cases in which we are happy with ALTER > TABLE's inheritance tree walking? IMHO, ALTER FOREIGN TABLE > always comes with some changes of the data source so implicitly > invoking of such commands should be defaultly turned off.
Imagine a case that foreign data source have attributes (A, B, C, D) but foreign tables and their parent ware defined as (A, B, C). If user wants to use D as well, ALTER TABLE parent ADD COLUMN D type would be useful (rather necessary?) to keep consistency. Changing data type from compatible one (i.e., int to numeric, varchar(n) to text), adding CHECK/NOT NULL constraint would be also possible. -- Shigeru HANADA -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers