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.92) (envelope-from ) id 1jCpgj-0001YR-K9 for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Mar 2020 19:09:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jCpgi-0000QS-DC for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Mar 2020 19:09:40 +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 1jCpgi-0000Pc-0y for pgsql-hackers@lists.postgresql.org; Fri, 13 Mar 2020 19:09:40 +0000 Received: from mail-qk1-x741.google.com ([2607:f8b0:4864:20::741]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jCpgf-0004QH-06 for pgsql-hackers@lists.postgresql.org; Fri, 13 Mar 2020 19:09:39 +0000 Received: by mail-qk1-x741.google.com with SMTP id x1so9591604qkx.10 for ; Fri, 13 Mar 2020 12:09:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=3sFrUndB2EHJt1IGacEmAbwyd5OXTZriljzb85qQj0M=; b=MeC9f1v1H6LuqxuZKsr4Q3vGjYceVTObBr1xHE/LP4oWVDGNxG8mpvAXdFRsFEFzbt WVdIwbRa0gS7HVJKKyL3dqhKFP84kwcN1CPy3cIv6357ai0k810vw8oyUuTpfIwfKPeZ Qrc9YOZypvAEjNmPVcOunxN7oG3jafqiYjgP0gpAqPBMRH2GbYnCrBd6Arg9XA3GGP+M czc7FRMhXLnguD1u39P9Ui1vp57BStRp9gR2RdIF26t3QPNT2XUHB1Udxd9/cUS6poNT +8JixiQkXI7JzKBIpsBhbiwDnhJbAu+HPoWvIhBzI9BtBjswpK5EcmnQz3IdplVl0pw2 n47Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=3sFrUndB2EHJt1IGacEmAbwyd5OXTZriljzb85qQj0M=; b=MPwXnN+g9qXiJ4Z7HLNQ9R4u55zcgvMQ83j0Ta6APVJtsoZWAhMXYCpdYoNpyF9sex eVtLc3J09xy/R8yv0YPbWHJKLPe1k6ldvTE1+Ze0j6/jteGQKrBWiJ5fCL6zmude6VJO gRNaCbonkJYPUI1LYQ8AWJO/rV/mt89VLz4jzSPLzbUmKdGQDfO9I9AnTmAG8Lj9DeBs fbWL1d5DuKgJO6kIIKIVVe6y7eSfCTAfGq3coEY+hlt6mdEVyVuoNu+Q4K3UAhMGtHvr bBS7MlkPUqrFwt7GmRRTpl9UpqaaW5RJfYJlIf6egnBOHTijbmmbpTjfRcuzMy9Av5yI j9Mw== X-Gm-Message-State: ANhLgQ1M3Skx1S8Sy6nj7e7Mu1pmkhpdsbp4OirV3nx5FkmLIyMhKFT6 NkCTTNXyyg5dW3yOi//uxQ62IA== X-Google-Smtp-Source: ADFU+vtz8emyjzw7KOvJFc6b2rUeu9hsyjvyOwDkJKxideMwgbZYmfmElSGIxHmCG96oxQ3VKRX6hQ== X-Received: by 2002:a37:6811:: with SMTP id d17mr14577097qkc.29.1584126574491; Fri, 13 Mar 2020 12:09:34 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.121.31.1]) by smtp.gmail.com with ESMTPSA id f22sm8656136qto.79.2020.03.13.12.09.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Mar 2020 12:09:33 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 3D8D3300898; Fri, 13 Mar 2020 16:09:31 -0300 (-03) Date: Fri, 13 Mar 2020 16:09:31 -0300 From: Alvaro Herrera To: James Coleman Cc: Tomas Vondra , Michael Paquier , Rafia Sabih , Peter Geoghegan , Simon Riggs , Shaun Thomas , Dmitry Dolgov <9erthalion6@gmail.com>, Alexander Korotkov , Tom Lane , PostgreSQL Developers Subject: Re: [PATCH] Incremental sort (was: PoC: Partial sort) Message-ID: <20200313190931.GA11508@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Mar-13, James Coleman wrote: > > I don't propose to commit 0003 of course, since it's not our policy; > > that's just to allow running pgindent sanely, which gives you 0004 > > (though my local pgindent has an unrelated fix). And after that you > > notice the issue that 0005 fixes. > > Is there a page on how you're supposed to run pgindent/when stuff like > this does get added/etc.? It's all a big mystery to me right now. > > Also, I noticed some of the pgindent changes aren't for changes in > this patch series; I have that as a separate patch, but not attached > because I see that running pgindent locally generates a massive patch, > so I'm assuming we just ignore those for now? Ah, I should have paid more attention to what I was attaching. Yeah, ideally you run pgindent and then only include the changes that are relevant to your patch series. We run pgindent across the whole tree once every release, so about yearly. Some commits go in that are not indented correctly, and those bother everyone -- I'm guilty of this myself more frequently than I'd like. You can specify a filelist to pgindent, also. What I do is super low-tech: do a "git diff origin/master", copy the filelist, and then ^V^E to paste that list into a command line to run pgindent (editing to remove the change histogram and irrelevant files). I should automate this ... -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services