Re: BUG #9001: Documentation bug

From: bricklen <bricklen(at)gmail(dot)com>
To: kai(dot)peters(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #9001: Documentation bug
Date: 2014-01-27 23:25:22
Message-ID: CAGrpgQ8=weF4nm76kdikPkR0n2X-91ov8xAUTmN8XUHJ_qEKkQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jan 27, 2014 at 8:38 AM, <kai(dot)peters(at)gmail(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 9001
> Logged by: Kai
> Email address: kai(dot)peters(at)gmail(dot)com
> PostgreSQL version: 9.3.2
> Operating system: Irrelevant
> Description:
>
> http://www.postgresql.org/docs/9.3/static/rangetypes.html
>
> 8.17.2. Examples
> CREATE TABLE reservation (room int, during tsrange);
> INSERT INTO reservation VALUES
> (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
>
> Bracket/paren mismatch in above INSERT statement
>
>
You are referring to '[2010...)' ? No, that's by design. See the section
http://www.postgresql.org/docs/9.3/static/rangetypes.html#RANGETYPES-IO
Also, if you test the example you can see that it works as shown.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-01-28 00:00:52 Re: BUG #9003: Hard-coding to localhost in postmaster
Previous Message Andres Freund 2014-01-27 23:20:50 Re: BUG #9003: Hard-coding to localhost in postmaster