Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wv7QA-0003qg-0w for pgsql-docs@arkaria.postgresql.org; Thu, 12 Jun 2014 16:00:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wv7Q9-0006wp-A5 for pgsql-docs@arkaria.postgresql.org; Thu, 12 Jun 2014 16:00:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Wv7Q8-0006wh-BK for pgsql-docs@postgresql.org; Thu, 12 Jun 2014 16:00:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Wv7Q2-00022H-04 for pgsql-docs@postgresql.org; Thu, 12 Jun 2014 16:00:06 +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 s5CG00pa026094; Thu, 12 Jun 2014 12:00:00 -0400 From: Tom Lane To: David G Johnston cc: pgsql-docs@postgresql.org Subject: Re: disabling log_rotation_age feature. In-reply-to: References: <53992FF8.2060702@po.ntts.co.jp> <23802.1402584095@sss.pgh.pa.us> Comments: In-reply-to David G Johnston message dated "Thu, 12 Jun 2014 08:35:16 -0700" Date: Thu, 12 Jun 2014 12:00:00 -0400 Message-ID: <26093.1402588800@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org David G Johnston writes: > On Thu, Jun 12, 2014 at 10:42 AM, Tom Lane-2 [via PostgreSQL] < > ml-node+s1045698n5807014h58@n5.nabble.com> wrote: >> I wonder if we should round fractions up instead of down in that logic? >> It might be less surprising for those GUCs where zero is special, and >> it seems like about a wash for most others. > ​I think documenting the behavior better, I don't. If you have to explain it, it probably needs improvement. > Green field maybe I'd say yes but given that the new behavior could turn > features on that are currently off it doesn't seem to be beneficial enough > to warrant changing. I don't think that argument holds water either. We routinely make changes that break old postgresql.conf files. Not in minor updates of course, but none of this is material for back-patching. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs