Re: BUG #18139: Causing FATAL error on database using function last() or first()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pyrotarlu74(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18139: Causing FATAL error on database using function last() or first()
Date: 2023-09-28 18:50:05
Message-ID: 1082093.1695927005@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> If I use the function last/first on this dataset, if the first rows parsed
> by the function contain null values, it cause FATAL error on database.

There is no last() nor first() function built into Postgres.
I surmise that you are using a buggy extension, in which case
you need to report this to the extension's author.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2023-09-28 19:36:18 Re: BUG #18139: Causing FATAL error on database using function last() or first()
Previous Message Tom Lane 2023-09-28 17:31:39 Re: BUG #18135: Incorrect memory access occurs when attaching a partition with an index