Re: BUG #5123: bug in window function "last_value"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andrey <andrey(at)ulab(dot)ru>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5123: bug in window function "last_value"
Date: 2009-10-16 17:28:57
Message-ID: 8519.1255714137@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Fetter <david(at)fetter(dot)org> writes:
> I think what the OP was expecting was to have the last value be 3
> instead of changing. This is at least a POLA violation.

[ shrug... ] It's what the spec requires, as far as anybody here
can tell. As Hitoshi-san already noted, we do point out in our
docs that last_value is not too useful unless you use a nondefault
window frame selection. I'm not sure what else we could do.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2009-10-16 17:53:34 Re: BUG #5118: start-status-insert-fatal
Previous Message Tom Lane 2009-10-16 17:02:09 Re: BUG #5121: Segmentation Fault when using pam w/ krb5