Re: Add RANGE with values and exclusions clauses to the Window Functions

From: David Fetter <david(at)fetter(dot)org>
To: Oliver Ford <ojford(at)gmail(dot)com>
Cc: Erik Rijkers <er(at)xs4all(dot)nl>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add RANGE with values and exclusions clauses to the Window Functions
Date: 2017-11-28 13:31:32
Message-ID: 20171128133132.GA24037@fetter.org
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Tue, Nov 28, 2017 at 10:51:19AM +0000, Oliver Ford wrote:
> On Tue, Nov 28, 2017 at 4:38 AM, David Fetter <david(at)fetter(dot)org> wrote:
> > I've taken the liberty of adding float8, somewhat mechanically. Do
> > the docs need some change, assuming that addition is useful?
> >
> > Best,
> > David.
> > --
> > David Fetter <david(at)fetter(dot)org> http://fetter.org/
> > Phone: +1 415 235 3778
>
> The SQL:2011 standard says that the range values should only be an
> integer or interval. My understanding is therefore that the ORDER BY
> columns should only be either an integer, with integer range values -
> or a date/time, with interval range values.
>
> I think if we go outside the standard we should leave it for another
> patch and further discussion. But maybe others would prefer to add
> support for more types even if they are non-standard?

I confess I was thinking more in terms of the use cases I recall from
back when I was training to be a scientist than the restrictions the
standard imposed.

Hapoy to make this extension separate if that's the consensus.

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-11-28 13:43:45 Re: ERROR: too many dynamic shared memory segments
Previous Message Ildus Kurbangaliev 2017-11-28 13:29:18 Re: [HACKERS] Custom compression methods