Re: Aggregates (last/first) not behaving

Wes Devauld <wes(at)devauld(dot)ca> wrote:

> I believe I lost the flavour of what I'm doing when I constructed this
> example. I'm not interested in the timepoint as much as the value that is
> attached to it. I need to be able to find the last chronological record for
> a given day.

> I can get the value for which I am looking in two steps:

> select max(t) as t into table last_of_day from test group by extract(day
> from t);
> select last_of_day.t, test.v from last_of_day, test where last_of_day.t =
> test.t;

> I was fairly happy when first() and last() were discovered, as these two
> steps could be merged, until the table grows too large and the query planner
> decides to sort the results before they are aggregated.

> I was searching for a way to keep using last() and keeping the extraction to
> a single step, although the more I fight with it, the less I think that it
> is worth it. If you have any further suggestions, I would appreciate
> hearing them.
> [...]

Perhaps you could /concisely/ rephrase your problem. Finding
the first/last value per group with/without window functions
is a common problem, and there are lots of solutions to it.
But few people will wade through lots of text to find out
what's bothering you.

For example, you can query the "last" values per day along
the lines of (untested):

| SELECT EXTRACT(day FROM t), v
| FROM test
| WHERE t IN (SELECT MAX(t) FROM test
| GROUP BY EXTRACT(day FROM t));

Obviously, this doesn't "keep using last()", so I don't know
whether it's good or bad for you.

Tim