Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9G3L-0001RO-VZ for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2014 15:30:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1W9G3L-0003QB-FI for pgsql-hackers@arkaria.postgresql.org; Fri, 31 Jan 2014 15:30:47 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9G3J-0003Q3-Kf for pgsql-hackers@postgresql.org; Fri, 31 Jan 2014 15:30:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1W9G3G-0008JK-63 for pgsql-hackers@postgresql.org; Fri, 31 Jan 2014 15:30:45 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s0VFUbD7014379; Fri, 31 Jan 2014 10:30:37 -0500 From: Tom Lane To: Stephen Frost cc: Robert Haas , Shigeru Hanada , Etsuro Fujita , PostgreSQL-development Subject: Re: inherit support for foreign tables In-reply-to: <20140131152136.GJ2921@tamriel.snowman.net> References: <52E5F3FD.6050000@lab.ntt.co.jp> <52E6137B.1080704@lab.ntt.co.jp> <32648.1391097891@sss.pgh.pa.us> <20275.1391119500@sss.pgh.pa.us> <20140131152136.GJ2921@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Fri, 31 Jan 2014 10:21:36 -0500" Date: Fri, 31 Jan 2014 10:30:37 -0500 Message-ID: <14378.1391182237@sss.pgh.pa.us> X-Pg-Spam-Score: -2.5 (--) 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 Stephen Frost writes: > I agree that using the FDW-specific options is the right approach and > disallowing those to be set on foreign tables makes sense. I don't > particularly like the idea of applying changes during inheiritance > which we wouldn't allow the user to do directly. While it might be a > no-op and no FDW might use it, it'd still be confusing. If we don't allow it directly, why not? Seems rather arbitrary. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers