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.
Date: Sun, 01 Oct 2023 21:09:05 -0400
Message-ID: <1899612.1696208945@sss.pgh.pa.us> (raw)
In-Reply-To: <7250ba53-f3b1-4e7a-a21d-3d9132772bbc@fastmail.com.au>
References: <7250ba53-f3b1-4e7a-a21d-3d9132772bbc@fastmail.com.au>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, matt_gibbins@fastmail.com.au, pgsql-performance@lists.postgresql.org
Subject: Re: Unexpected termination looping over table.
In-Reply-To: <1899612.1696208945@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox