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 1tYSGQ-00AybU-6b for pgsql-bugs@arkaria.postgresql.org; Thu, 16 Jan 2025 15:58:34 +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 1tYSGO-00FFVu-DU for pgsql-bugs@arkaria.postgresql.org; Thu, 16 Jan 2025 15:58:32 +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 1tYSGO-00FFVm-5B for pgsql-bugs@lists.postgresql.org; Thu, 16 Jan 2025 15:58:32 +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.96) (envelope-from ) id 1tYSGN-000jfV-15 for pgsql-bugs@lists.postgresql.org; Thu, 16 Jan 2025 15:58:31 +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 50GFwSLN1623378; Thu, 16 Jan 2025 10:58:28 -0500 From: Tom Lane To: Vik Fearing cc: Rajni Bobal , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18774: Not the required output of the query used in the function(delete_from_table1) in postgresql9.4 In-reply-to: <6afb2dff-e171-47d1-b59a-8a062e18f20e@postgresfriends.org> References: <18774-a34a84b302e95de9@postgresql.org> <6afb2dff-e171-47d1-b59a-8a062e18f20e@postgresfriends.org> Comments: In-reply-to Vik Fearing message dated "Thu, 16 Jan 2025 15:55:25 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1623376.1737043108.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Thu, 16 Jan 2025 10:58:28 -0500 Message-ID: <1623377.1737043108@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Vik Fearing writes: > #18776 appears to have been discarded as a duplicate.  In any case, no > one is going to fix a bug in 9.4 which has been EOL since 2020.  I > suggest you upgrade to a supported version and re-report the bug if it > still exists. If you do reproduce your problem on a still-in-support branch, please re-file with a *self-contained* test case. It's impossible for someone to reverse-engineer your problem from just the two function definitions, with no table declarations, sample data, calling sequence, or expected vs. actual results. https://wiki.postgresql.org/wiki/Guide_to_reporting_problems If it's difficult to cram all the details into our bug-reporting form, personally I'd ignore the form and just send mail to pgsql-bugs@lists.postgresql.org regards, tom lane