Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hIfUN-00021P-LF for pgsql-committers@arkaria.postgresql.org; Mon, 22 Apr 2019 20:24:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hIfUM-0001ve-BC for pgsql-committers@arkaria.postgresql.org; Mon, 22 Apr 2019 20:24:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hIfUM-0001vU-4l; Mon, 22 Apr 2019 20:24:30 +0000 Received: from mail-lf1-x143.google.com ([2a00:1450:4864:20::143]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hIfUJ-0005d7-K1; Mon, 22 Apr 2019 20:24:29 +0000 Received: by mail-lf1-x143.google.com with SMTP id u17so9919974lfi.3; Mon, 22 Apr 2019 13:24:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ok4LcQmt+pon+NAIu4ynR39iUu1xT+hrBHKn5ltDSeE=; b=JCai9+r6uGln46g8l9/xdEdLar+lbUQkgV6I4geYJZM39NOFXaodaPH5WETzex3yOZ NyVUom3TzV0PeQb2rigeoU7OyOlYUzL7wag6LfZj052CH4CGw07K0nCpRLn2opm+4Qpy PqYgJsz3q7PVgd6EYkxx3r3O9Z5bvJJ4gN8xoK/rr+evyD5cOYY1k9v4er6NvV6loa0I xVcpkJLK9Zz3+5qSIHTwoBT9aUFUjozB7F0oQDgnsB9GH0T4E2cLdQHKKLxHyHRU8uF9 jfAfJfFUEZJOdpNY/RjjiS3o89xtiw/N6LcVzXUNFkACWfG5o6vw/xby1jYofoTqanIh y1+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ok4LcQmt+pon+NAIu4ynR39iUu1xT+hrBHKn5ltDSeE=; b=X784B8So2v0YpXwHfXvYT465rQqcFKIrb6uNCXO5kNWWswctk05wmMpWWSO/hnGJ1d aOmR8fCyvQrv7+w9fPJiERZoJv1PK0DYqXh4zskh3P9lixiYk/vF9HP0YPPPIZgNR8D9 ZnlBCwo63IYsE1E7GNzWMTIU8aSnJIk1XXLkbi5uhdlRv6sPuYQCVWpLLMULlLBCWxKg MmFVmx0ABG8ZvOm030k8qs+sQB+EJNf7n3kzXvv3ZmdCRgyMZAGIl/ZEhOCd0e8KPmpr ICQFxQPbBqE7rOgxp8FUWSaNJqYfFdz7wSOq9HmqnYc5Sw/57rF5Fqu1WuGNLe17KLAZ J6Nw== X-Gm-Message-State: APjAAAXSkxf7azlJhLMl2v2XE795DtFDGS2QHytOL3pbnoZCWjJPhwdE /4YuykAfjWcpnOFbhaD+6e7h8nXfTm+sUjnzxQ2yW2V6 X-Google-Smtp-Source: APXvYqwPwzm79J09pQVnFzyqh7JggbaW61cDH/KqHro0+3r1DY2PnuDIg42QnNOUzOCqC9mFrPBlWugFt5aX9yC65X0= X-Received: by 2002:ac2:4242:: with SMTP id m2mr11154754lfl.142.1555964667091; Mon, 22 Apr 2019 13:24:27 -0700 (PDT) MIME-Version: 1.0 References: <5CBDB770.2060602@lab.ntt.co.jp> In-Reply-To: From: Robert Haas Date: Mon, 22 Apr 2019 16:24:15 -0400 Message-ID: Subject: Re: pgsql: Allow insert and update tuple routing and COPY for foreign table To: Laurenz Albe Cc: Etsuro Fujita , pgsql-committers , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Apr 22, 2019 at 3:37 PM Laurenz Albe wrote: > Sure, it is not hard to modify a FDW to continue working with v11. > > My point is that this should not be necessary. I'm not sure whether this proposal is a good idea or a bad idea, but I think that it's inevitable that FDWs are going to need some updating for new releases as the API evolves. That has happened before and will continue to happen. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company