Re: BUG #8367: wrong example in 8.17.10

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: koizumistr(at)minos(dot)ocn(dot)ne(dot)jp, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8367: wrong example in 8.17.10
Date: 2013-09-03 01:54:08
Message-ID: 1378173248.19551.2.camel@jdavis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 2013-08-06 at 12:27 -0400, Tom Lane wrote:
> koizumistr(at)minos(dot)ocn(dot)ne(dot)jp writes:
> > In 8.17.10 "Constraints on Ranges" of PostgreSQL 9.2.4 Documentation, a
> > constraint will prevent the overlapping values in an example.
> > But in the example, range [2010-01-01 11:30, 2010-01-01 13:00) and range
> > [2010-01-01 14:45, 2010-01-01 15:45) do not overlap.
>
> No, but the second one overlaps with the range value shown in 8.17.2.
> So this is correct if it's understood as a continuation of that example.
> Still, it's kind of a long way from 8.17.2 to 8.17.10. It might be better
> if this section were recast to use a standalone example --- Jeff, what do
> you think?

That sounds reasonable, patch attached. Minor change, so if nobody has
any more suggestions I'll commit it tomorrow night.

Regards,
Jeff Davis

Attachment Content-Type Size
rangetypes-example.patch text/x-patch 3.0 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message info 2013-09-03 09:08:44 phpPgAdmin
Previous Message Michael Paquier 2013-09-01 13:16:18 Re: BUG #8408: Not exactly correct error messages for failed check in presence of dropped columns.