Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Wv7fk-0004TG-3e for pgsql-docs@arkaria.postgresql.org; Thu, 12 Jun 2014 16:16:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Wv7fj-00050u-Fd for pgsql-docs@arkaria.postgresql.org; Thu, 12 Jun 2014 16:16:15 +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 1Wv7fh-0004xt-MP for pgsql-docs@postgresql.org; Thu, 12 Jun 2014 16:16:13 +0000 Received: from mail-we0-x233.google.com ([2a00:1450:400c:c03::233]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Wv7fe-0002OC-5o for pgsql-docs@postgresql.org; Thu, 12 Jun 2014 16:16:11 +0000 Received: by mail-we0-f179.google.com with SMTP id w62so1591682wes.10 for ; Thu, 12 Jun 2014 09:16:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6FO6rx+QpVtivxr9WIFL0WSL7T23O7K6J7kEn1dL1bU=; b=J0C/5fk+P3OvC24yDmalP8IWA2UwmIyDTTekz87LiBcqthGIwJaMfOnoHw+DrEwptU Rn18bbjQOcnqMJ5DLiFWcbguctOkUlKq3oDsNpZYfVMkSSePKP1ru5Y1V5PjYD8JsLdC vPc9nyes6U/nH4omnAAAhJpwxw+25uKkaedkNnzLI7oOe3n5rxC9GhChTfUv0L3zOq4n NgAu+KaM1E5w/h0MhDYeje5tADnKSlC4vWFTi6+CxhtEcsPIJewzI0DinMl4W4qXEKwO ri03e20ZHqZLQd4+3xKLu5JnxqQzg+VodE31jOR50BEgZKeNrCXCyUMs6RWGUzLcvmVI EfGg== MIME-Version: 1.0 X-Received: by 10.180.84.226 with SMTP id c2mr8016635wiz.50.1402589768035; Thu, 12 Jun 2014 09:16:08 -0700 (PDT) Received: by 10.217.1.145 with HTTP; Thu, 12 Jun 2014 09:16:07 -0700 (PDT) In-Reply-To: <26093.1402588800@sss.pgh.pa.us> References: <53992FF8.2060702@po.ntts.co.jp> <23802.1402584095@sss.pgh.pa.us> <26093.1402588800@sss.pgh.pa.us> Date: Thu, 12 Jun 2014 12:16:07 -0400 Message-ID: Subject: Re: disabling log_rotation_age feature. From: David Johnston To: Tom Lane Cc: "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary=f46d044280dee3ba2704fba5e0d0 X-Pg-Spam-Score: -2.0 (--) 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 --f46d044280dee3ba2704fba5e0d0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thursday, June 12, 2014, Tom Lane wrote: > 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. > > > =E2=80=8BI think documenting the behavior better, > > I don't. If you have to explain it, it probably needs improvement. No argument with the philosophy. > > > Green field maybe I'd say yes but given that the new behavior could tur= n > > 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. > Then I'd pick throwing an error if a floating point value is assigned to a parameter that is defined to accept integer. I'd rather actually break the file and not silently redefine its contents. David J. --f46d044280dee3ba2704fba5e0d0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thursday, June 12, 2014, Tom Lane <tgl@sss.pgh.pa.us> wrote:
David= G Johnston <david.g.johnston@gmail.com>= ; writes:
> On Thu, Jun 12, 2014 at 10:42 AM, Tom Lane-2 [via PostgreSQL] <
> ml-node+s1045698n5807014h58@n= 5.nabble.com> wrote:
>> I wonder if we should round fractions up instead of down in that l= ogic?
>> It might be less surprising for those GUCs where zero is special, = and
>> it seems like about a wash for most others.

> =E2=80=8BI think documenting the behavior better,

I don't. =C2=A0If you have to explain it, it probably needs improvement= .

No argument with the philosophy.
=C2=A0

> Green field maybe I'd say yes but given that the new behavior coul= d turn
> features on that are currently off it doesn't seem to be beneficia= l enough
> to warrant changing.

I don't think that argument holds water either. =C2=A0We routinely make=
changes that break old postgresql.conf files. =C2=A0Not in minor updates of course, but none of this=C2=A0is material for back-patching.

Then=C2=A0I'd pick throwing an error if a floa= ting point value is assigned to a parameter that is defined to accept integ= er. I'd rather actually break the file and not silently redefine its co= ntents.

David J.

=C2=A0
--f46d044280dee3ba2704fba5e0d0--