Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WGkcU-0003F5-TG for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Feb 2014 07:34:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WGkcU-000545-8M for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Feb 2014 07:34:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WGkcS-00053v-Mc for pgsql-hackers@postgresql.org; Fri, 21 Feb 2014 07:34:00 +0000 Received: from tama500.ecl.ntt.co.jp ([129.60.39.148]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WGkcM-0006sy-ES for pgsql-hackers@postgresql.org; Fri, 21 Feb 2014 07:34:00 +0000 Received: from mfs5.rdh.ecl.ntt.co.jp (mfs5.rdh.ecl.ntt.co.jp [129.60.39.144]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id s1L7Xo3B022633; Fri, 21 Feb 2014 16:33:50 +0900 Received: from mfs5.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id D2768E011A; Fri, 21 Feb 2014 16:33:50 +0900 (JST) Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs5.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id BC37BE0119; Fri, 21 Feb 2014 16:33:50 +0900 (JST) Received: from [129.60.241.197] ([129.60.241.197]) by imail3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id s1L7XoCx026766; Fri, 21 Feb 2014 16:33:50 +0900 Message-ID: <5307014C.4070605@lab.ntt.co.jp> Date: Fri, 21 Feb 2014 16:33:32 +0900 From: Etsuro Fujita User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Kyotaro HORIGUCHI CC: shigeru.hanada@gmail.com, pgsql-hackers@postgresql.org Subject: Re: inherit support for foreign tables References: <20140220.154736.15628889.horiguchi.kyotaro@lab.ntt.co.jp> <5305DF28.1010308@lab.ntt.co.jp> <5306BC08.2000009@lab.ntt.co.jp> <20140221.152321.92712524.horiguchi.kyotaro@lab.ntt.co.jp> In-Reply-To: <20140221.152321.92712524.horiguchi.kyotaro@lab.ntt.co.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-MML: No X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org (2014/02/21 15:23), Kyotaro HORIGUCHI wrote: >>>> NOTICE: Child foregn table child01 is affected. >>>> NOTICE: Child foregn table child02 is affected >>>> NOTICE: Child foregn table child03 rejected 'alter tempmin set >>>> default' >>>> >>>> What do you think about this? It looks a bit too loud for me >>>> though... >>> >>> I think that's a good idea. >> >> I just thought those messages would be shown for the user to readily >> notice the changes of the structures of child tables that are foreign, >> done by the recursive altering operation. But I overlooked the third >> line: >> >> NOTICE: Child foregn table child03 rejected 'alter tempmin set >> default' >> >> What does "rejected" in this message mean? > > It says that child03 had no ability to perform the requested > action, in this case setting a default value. It might be better > to reject ALTER on the parent as a whole when any children > doesn't accept any action. Now understood, thougn I'm not sure it's worth implementing such a checking mechanism in the recursive altering operation... Thanks, Best regards, Etsuro Fujita -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers