Re: Can't figure out how to use now() in default for tsrange column (PG 9.2) - Mailing list pgsql-general

From Daniele Varrazzo
Subject Re: Can't figure out how to use now() in default for tsrange column (PG 9.2)
Date
Msg-id CA+mi_8b7FdqkLBKRS0QmSQOjak-BjsMx-uqT_yRTA4_qQ0mYRw@mail.gmail.com
Whole thread Raw
In response to Re: Can't figure out how to use now() in default for tsrange column (PG 9.2)  (Craig Ringer <ringerc@ringerc.id.au>)
Responses Re: Can't figure out how to use now() in default for tsrange column (PG 9.2)  (Alban Hertroys <haramrae@gmail.com>)
List pgsql-general
On Mon, Jul 16, 2012 at 3:56 PM, Craig Ringer <ringerc@ringerc.id.au> wrote:
> On 07/16/2012 07:41 PM, Alban Hertroys wrote:
>>>>
>>>> BTW, that second value looks a whole lot like a poorly thought out

> Yup. The 'infinity' value doesn't play well with all database access APIs
> and languages, though.

It doesn't even play well with PostgreSQL's extract(). I reported it
some times ago but as of 9.1.4 it has not been fixed.

=# select extract(epoch from 'infinity'::timestamp);
 date_part
-----------
         0

This makes 'infinity' a problematic choice in any application
requiring a mapping between dates and reals, such as when using
intervals in gist indexes.

-- Daniele

pgsql-general by date:

Previous
From: Chris Angelico
Date:
Subject: Re: Replication/cloning: rsync vs modification dates?
Next
From: Michael Nolan
Date:
Subject: Re: Replication/cloning: rsync vs modification dates?