Sorry for wasting your time, I now see: If frame_end is omitted it defaults
to CURRENT ROW.
clearly in the documentation. I made the assumption that the default was
UNBOUNDED PROCEDING/FOLLOWING which is now very obviously not the case.
Again, sorry for not really taking the time to ensure this
w...@devauld.ca writes:
> -- The last_value(0 window function appears to be changing values
> -- mid window. An example is detailed below.
So far as I can see, these results are correct per spec. Note the
caution in the manual about these window functions:
Note that first_value, last_value, a
> -Original Message-
> From: pgsql-bugs-ow...@postgresql.org [mailto:pgsql-bugs-
> ow...@postgresql.org] On Behalf Of w...@devauld.ca
> Sent: Tuesday, November 20, 2012 10:28 AM
> To: pgsql-bugs@postgresql.org
> Subject: [BUGS] BUG #7685: last_value() not consistent
The following bug has been logged on the website:
Bug reference: 7685
Logged by: Wes Devauld
Email address: w...@devauld.ca
PostgreSQL version: 9.2.1
Operating system: Windows 7 Enterprise
Description:
-- The last_value(0 window function appears to be changing values
