Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1et8yj-00059y-2p for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Mar 2018 09:33:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1et8yi-0005w8-6w for pgsql-hackers@arkaria.postgresql.org; Tue, 06 Mar 2018 09:33:48 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1et8sx-0006kV-Sf for pgsql-hackers@lists.postgresql.org; Tue, 06 Mar 2018 09:27:52 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1et8st-0003Gz-JN for pgsql-hackers@postgresql.org; Tue, 06 Mar 2018 09:27:50 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 288E421C1C8D; Tue, 6 Mar 2018 12:27:45 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from [192.168.27.132] (gw.postgrespro.ru [93.174.131.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id D072A21C1C8C; Tue, 6 Mar 2018 12:27:44 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1520328464; bh=yQ7tWcMttgbqML/oM6e04tKDpkVnvbiibaFZd5JFlPw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=FqCdLp/oeG0EajViHKkqNLsU/X/FjqCqbtfECJ/Nzxba8DW7h0BFy4dEOmbjjnUkf jFgdPRsNKc4LiEAIPzK+upEo4l0975xd2QXYQxA6EUt4uOrokl7TNCnEhKCwIDiD7n vcK/uRiEnOZwu3cvrZ5uF7aw85FHvtTW/08OzGpE= Subject: Re: [HACKERS] PoC: full merge join on comparison clause To: Ashutosh Bapat Cc: pgsql-hackers , Jeff Davis References: <22906fd3-6f56-2473-9897-21a9532e6da3@postgrespro.ru> <0e0a0cb9-f51e-f8a6-3829-50c3e38e33f9@postgrespro.ru> <715cb811-4538-9967-a2e3-ca85f2711d80@postgrespro.ru> <636d3f40-be16-78cc-717f-b85e9f1b9362@postgrespro.ru> <20180123163126.GK2416@tamriel.snowman.net> <53625d9e-b608-bd9d-86a2-f560c02aff7f@postgrespro.ru> <513df2b9-b068-6cf4-895e-adb3968547e0@postgrespro.ru> <8c762bb0-1507-5ac1-b408-b942416416bf@postgrespro.ru> From: Alexander Kuzmenkov Message-ID: <36d18491-579e-e54b-96bb-4cba38c5a544@postgrespro.ru> Date: Tue, 6 Mar 2018 12:27:44 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 05.03.2018 08:30, Ashutosh Bapat wrote: > But creating such patches using git format-patch (with -v as some suggest) really > helps in general. > Thanks for the advice. I heard about this workflow, but never used it myself. Perhaps it's time to try it. -- Alexander Kuzmenkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company