Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlw5U-004vnc-Cq for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Sep 2023 18:50:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlw5T-00FXgn-5c for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Sep 2023 18:50:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlw5S-00FXgP-So for pgsql-bugs@lists.postgresql.org; Thu, 28 Sep 2023 18:50:10 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlw5P-007AAG-1S for pgsql-bugs@lists.postgresql.org; Thu, 28 Sep 2023 18:50:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 38SIo5O51082094; Thu, 28 Sep 2023 14:50:05 -0400 From: Tom Lane To: pyrotarlu74@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18139: Causing FATAL error on database using function last() or first() In-reply-to: <18139-9f45531e1ce99975@postgresql.org> References: <18139-9f45531e1ce99975@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 28 Sep 2023 17:02:51 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1082092.1695927005.1@sss.pgh.pa.us> Date: Thu, 28 Sep 2023 14:50:05 -0400 Message-ID: <1082093.1695927005@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form 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