Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpzEx-00013l-WA for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Aug 2018 17:05:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fpzEw-0002i1-7W for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Aug 2018 17:05:46 +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 1fpzEw-0002hu-0u for pgsql-hackers@lists.postgresql.org; Wed, 15 Aug 2018 17:05:46 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpzEt-0002RF-BI for pgsql-hackers@lists.postgresql.org; Wed, 15 Aug 2018 17:05:45 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w7FH5dib013170; Wed, 15 Aug 2018 13:05:39 -0400 From: Tom Lane To: Alvaro Herrera cc: Robert Haas , PostgreSQL Hackers Subject: Re: C99 compliance for src/port/snprintf.c In-reply-to: <20180815155643.zx4qpcmpvhemefyg@alvherre.pgsql> References: <20180815155643.zx4qpcmpvhemefyg@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Wed, 15 Aug 2018 12:56:43 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <13168.1534352739.1@sss.pgh.pa.us> Date: Wed, 15 Aug 2018 13:05:39 -0400 Message-ID: <13169.1534352739@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alvaro Herrera writes: > On 2018-Aug-15, Robert Haas wrote: >> Back-patching seems a bit aggressive to me considering that the danger >> is hypothetical. > That was my first thought too, and my preferred path would be to make > this master-only and only consider a backpatch later if we find some > practical reason to do so. Meh --- the hazards of back-patching seem to me to be more hypothetical than the benefits. Still, I seem to be in the minority, so I withdraw the proposal to back-patch. regards, tom lane