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 1qn8nD-009wfm-TQ for pgsql-performance@arkaria.postgresql.org; Mon, 02 Oct 2023 02:36:20 +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 1qn8nC-00GECo-GP for pgsql-performance@arkaria.postgresql.org; Mon, 02 Oct 2023 02:36:18 +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 1qn8nB-00GECD-48 for pgsql-performance@lists.postgresql.org; Mon, 02 Oct 2023 02:36:18 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qn8n7-007hhL-Am for pgsql-performance@lists.postgresql.org; Mon, 02 Oct 2023 02:36:15 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4D9BC5C02DC; Sun, 1 Oct 2023 22:36:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 01 Oct 2023 22:36:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com.au; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm2; t=1696214172; x=1696300572; bh=9v+QVd/b9SLi2Ywwq5GAlUT59 bwwHwP2bJKu7cBvp4o=; b=fA3UWY5uoTmtlwWMYfWaiWDB0uRr2bNaxClouT4aT yxtuc9vMt6sR6cZNuLHnx831EHlkUU8WeYOVW/T9XSQ5JrBefsBczaC7e2rTlplD BG87R4w7bQeMmD3VZbz+kE71Mb7IUjrax5KTzM6l8cmeoD9CxNLiVz8ueflqT/wU OamzSz0oxjA11VEDz2PXCvuszRGwJUoAtGLrwoeXlzHF/pYYI0T4wW7KasfhbpyC 4+iNizx6c3liHvCpDEOYM/SDo1ax7vxYY1tpfo7K0g0WSqWCbZy+H0Ro4uedfIIr ODo7S9YpXVAkjUvrUqzJk+gPfXSsL3QwtlaWkjhvWN/GA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t= 1696214172; x=1696300572; bh=9v+QVd/b9SLi2Ywwq5GAlUT59bwwHwP2bJK u7cBvp4o=; b=pT/N8gptyPVpsxFPK5pH5JCvVg4MRWja0dhIqxyEFsJLYGwuuX9 St8Aw3d3SycKPN0crOUMw/dNZmaIJoT6Mgl7qGe0kCI9PvW5uSjNihaVZ9TwEc6X LLuddLAw9AJgf67w9kDjTCG4WkCIWZA+Y1G5/DkwfW2OVnOKo7XUUCW1v96eioFs ptbGCtvzDCWN8h3500Tp7rv7yAR5tr7D/91YQ4KNKOKtGDgVyPsYytdlLwOy/ZoG MsdrbPcL+et94pSy5sDMfeDzIGYX5ZotxsgfxJN4RNSG8cX/69vxXQJgaXBsZ7bX z1wIkV/lrsubkuc47tr7mMkFNRGdO6aw24Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeigddthecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvvehfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpeforghtthcuifhisggsihhnshcuoehmrghtthgpghhisggs ihhnshesfhgrshhtmhgrihhlrdgtohhmrdgruheqnecuggftrfgrthhtvghrnhepjefftd eufedtfeeujefffefgleduvdejhefhudeujeffieevheeiffdtkeehjefgnecuffhomhgr ihhnpegrphgrtghhvgdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehmrghtthgpghhisggsihhnshesfhgrshhtmhgrihhlrdgtohhm rdgruh X-ME-Proxy: Feedback-ID: i6d194797:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 1 Oct 2023 22:36:10 -0400 (EDT) Message-ID: <009d1bdd-0e93-4e36-9d2c-aa02dfd5e015@fastmail.com.au> Date: Mon, 2 Oct 2023 13:36:06 +1100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Unexpected termination looping over table. Content-Language: en-AU To: Tom Lane Cc: pgsql-performance@lists.postgresql.org References: <7250ba53-f3b1-4e7a-a21d-3d9132772bbc@fastmail.com.au> <1899612.1696208945@sss.pgh.pa.us> From: Matt Gibbins In-Reply-To: <1899612.1696208945@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2/10/23 12:09, Tom Lane wrote: > Matt Gibbins writes: >> Have encountered an intriguing issue processing a table with a large >> number of rows. The process is to loop over the table processing each >> row executing the Apache AGE cypher function over each row >> individually.The looping is necessary because of encountering a limit on >> the number of rows that the cypher function would process. >> The process terminates unexpectedly with the following message. Notable >> that it runs for quite some time before termination.: >> SQL Error [42703]: ERROR: could not find rte for >> a01a724103fbb3d059b8387bf043dbc8 >>   Where: PL/pgSQL function >> analysis.create_trips(text,text,text,text,text,text,integer,text,integer) >> line 5 at EXECUTE > There is no occurrence of "could not find rte" anywhere in the > core Postgres source code. I surmise that you're using some > extension that isn't happy. > > regards, tom lane Tom Thanks for your response. I am using the Apache AGE extension which enables graph data processing on PostgreSQL. https://age.apache.org/ I'll enquire with the Apache AGE list for an answer. Regards Matt.