From: Tom Lane <tgl@sss.pgh.pa.us>
To: Matt Gibbins <matt_gibbins@fastmail.com.au>
cc: pgsql-performance@lists.postgresql.org
Subject: Re: Unexpected termination looping over table.
In-reply-to: <7250ba53-f3b1-4e7a-a21d-3d9132772bbc@fastmail.com.au>
References: <7250ba53-f3b1-4e7a-a21d-3d9132772bbc@fastmail.com.au>
Comments: In-reply-to Matt Gibbins <matt_gibbins@fastmail.com.au>
	message dated "Mon, 02 Oct 2023 11:57:01 +1100"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <1899611.1696208945.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Sun, 01 Oct 2023 21:09:05 -0400
Message-ID: <1899612.1696208945@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1899612.1696208945%40sss.pgh.pa.us>
Precedence: bulk

Matt Gibbins <matt_gibbins@fastmail.com.au> 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