| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matt Gibbins <matt_gibbins(at)fastmail(dot)com(dot)au> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Unexpected termination looping over table. |
| Date: | 2023-10-02 01:09:05 |
| Message-ID: | 1899612.1696208945@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Matt Gibbins <matt_gibbins(at)fastmail(dot)com(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Gibbins | 2023-10-02 02:36:06 | Re: Unexpected termination looping over table. |
| Previous Message | Matt Gibbins | 2023-10-02 00:57:01 | Unexpected termination looping over table. |