Re: lag_until_you_get_something() OVER () window function

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Kirk Roybal <kirk(at)webfinish(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lag_until_you_get_something() OVER () window function
Date: 2014-10-29 19:09:25
Message-ID: CAHyXU0zwxgmTPditwzjytxY2F+O68GU7oQ8qVcrKcGxMFkoCtg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 29, 2014 at 12:04 PM, Kirk Roybal <kirk(at)webfinish(dot)com> wrote:
> This [custom aggregate gapfill] is a pretty elegant way of getting there.
>
> It also does a better job of respecting the window frame.
>
> I'll use this until this
> https://commitfest.postgresql.org/action/patch_view?id=1096 shows up.

Yes. In fact it turns out you can implement all kinds of things
including gaps in standards support by via the combination of windows
functions + custom aggregates. Performance is pretty good but not
great.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-10-29 19:09:27 Re: Lockless StrategyGetBuffer() clock sweep
Previous Message Andres Freund 2014-10-29 19:07:06 Re: pg_background (and more parallelism infrastructure patches)