Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oXpv4-0001PR-GP for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Sep 2022 20:20:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oXpv2-0000LR-8E for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Sep 2022 20:20:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oXpv1-0000LA-V9 for pgsql-hackers@lists.postgresql.org; Mon, 12 Sep 2022 20:20:35 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oXpuw-00039D-NN for pgsql-hackers@lists.postgresql.org; Mon, 12 Sep 2022 20:20:32 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 28CKKQq11778777; Mon, 12 Sep 2022 16:20:26 -0400 From: Tom Lane To: =?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= cc: Andres Freund , Michael Paquier , pgsql-hackers@lists.postgresql.org Subject: Re: Splitting up guc.c In-reply-to: <87v8psl5d8.fsf@wibble.ilmari.org> References: <587607.1662836699@sss.pgh.pa.us> <666417.1662862120@sss.pgh.pa.us> <925946.1662918775@sss.pgh.pa.us> <1305798.1662935501@sss.pgh.pa.us> <20220912193928.wgrccx4b4k3solpu@awork3.anarazel.de> <1771845.1663011970@sss.pgh.pa.us> <87v8psl5d8.fsf@wibble.ilmari.org> Comments: In-reply-to =?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= message dated "Mon, 12 Sep 2022 21:12:03 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1778775.1663014026.1@sss.pgh.pa.us> Date: Mon, 12 Sep 2022 16:20:26 -0400 Message-ID: <1778776.1663014026@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?utf-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= writes: > Git can detect more complicated code movement (see the `--color-moved` > option to `git diff`), but I'm not sure it's clever enough to realise > that a change modifying a block of code that was moved in the meanwhile > should be applied at the new destination. Yeah, I suspect people will have to manually reapply any changes in the GUC tables to guc_tables.c. That'll be the same amount of work for them whenever we commit this patch (unless theirs lands first, in which case I have to deal with it). The issue I think is whether it's politer to make that happen during a CF or between CFs. regards, tom lane