Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d0MhH-00020D-Lv for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Apr 2017 06:33:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d0MhH-0004JQ-8m for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Apr 2017 06:33:07 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d0Mfj-0007RI-RD for pgsql-hackers@postgresql.org; Tue, 18 Apr 2017 06:31:32 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d0Mfg-0001v6-6p for pgsql-hackers@postgresql.org; Tue, 18 Apr 2017 06:31:30 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 5041121C26EF; Tue, 18 Apr 2017 09:31:25 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru Received: from localhost (unknown [92.243.181.54]) by mail.postgrespro.ru (Postfix) with ESMTPSA id 1EBD021C257A; Tue, 18 Apr 2017 09:31:25 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1492497085; bh=/NC0vX58oZrNE3YEgykKyWRA4TAcQathJCeu1MDZw38=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=CWKukvQ7jWKNaGsd82SaqWeK9rBLbxS6yUZHmvz/mh6U3Fk3GFOu4GRSFcXLk8Ezd bXpfLXAkSMODl2ez6GfTLkTUndXTSdwxhgg2rtseXOxanSVvqDtFRDs1RAEXbmwJuR whO5/cXl6YfIU7/hvexu+rakDYwOAOwIHtve4XtM= From: Dmitry Ivanov To: Tom Lane Cc: Dmitry Ivanov , pgsql-hackers Subject: Re: Possible problem in Custom Scan API Date: Tue, 18 Apr 2017 09:30:53 +0300 MIME-Version: 1.0 Message-ID: <1dc20861-189b-4349-bb2e-9bfb2c86bb9f@postgrespro.ru> In-Reply-To: <29429.1492457615@sss.pgh.pa.us> References: <20021.1491933424@sss.pgh.pa.us> <1ef85b46-1385-4810-bb80-97cd977da1d5@postgrespro.ru> <367.1491940070@sss.pgh.pa.us> <4509.1491944329@sss.pgh.pa.us> <0e0388a6-aa53-42a6-8be9-0d46ccbc788e@postgrespro.ru> <8130.1492013026@sss.pgh.pa.us> <29429.1492457615@sss.pgh.pa.us> Organization: Postgres Professional User-Agent: Trojita/0.7; Qt/5.8.0; xcb; Linux; Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.0 (--) 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 Tom Lane wrote: > I'm unimpressed by this part --- we couldn't back-patch such a change, and > I think it's unnecessary anyway in 9.6+ because the scan provider could > generate a nondefault pathtarget if it wants this to happen. You're right, of course. Thank you very much! --=20 Dmitry Ivanov Postgres Professional: http://www.postgrespro.com Russian Postgres Company --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers