Re: pgsql: Clarify that a non-specified precision NUMERIC has a very high r

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Clarify that a non-specified precision NUMERIC has a very high r
Date: 2011-04-27 03:45:56
Message-ID: 201104270345.p3R3juE01906@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > On Tue, Apr 26, 2011 at 1:28 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> I removed the extra "the", and I didn't think people were clear you
> >> could just specify NUMERIC alone. We know you can you can do things
> >> like VARCHAR, but others will probably not realize it so I wanted to
> >> explicity mention it. Other wording?
>
> > Oh, good catch. I agree that removing the extra "the" is a good
> > change, but I think you should remove the parenthetical phrase you
> > added.
>
> I agree, the parenthetical phrase is entirely redundant with the earlier
> part of the sentence; or if you must have it, it belongs after
> "otherwise", not where it is.
>
> Also, could we spell "explicitly" correctly?

OK, spelling fixed, and paragraph paired down:

The maximum allowed precision when explicitly specified in the
type declaration is 1000; <type>NUMERIC</type> with no specified
precision is subject to the limits described in <xref
linkend="datatype-numeric-table">.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2011-04-27 04:07:05 pgsql: Doc wording improvement for NUMERIC limit paragraph.
Previous Message Bruce Momjian 2011-04-27 03:43:46 pgsql: Reword documentation for NUMERIC with no specified precision.