From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | iuritomazini(dot)dev(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18563: Where is tha "FIRST" aggregate function?? |
Date: | 2024-08-01 19:23:29 |
Message-ID: | 3781617.1722540209@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Christophe Pettus <xof(at)thebuild(dot)com> writes:
>> On Aug 1, 2024, at 09:25, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
>> I am migrating for
>> other database, bacause of the dificulty to get a similar resource to
>> substitute the "FIRST" in PostgreSQL and I hope you can recognize this bad
>> error and implement something to suppply this lack. Good bye!
> It's trivial to implement in PostgreSQL:
> https://wiki.postgresql.org/wiki/First/last_(aggregate)
The built-in (since v16) "any_value()" aggregate is actually just like
what that page shows for "first()". The name is chosen to reflect the
fact that the aggregate itself isn't promising anything: you have to
use it in the correct way to get useful behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-08-01 19:34:55 | Re: BUG #18564: Incorrect sorting with using NULLS LAST (NULLS FIRST) |
Previous Message | Weatherby,Gerard | 2024-08-01 17:55:23 | PL/python event_trigger |