On Fri, Mar 22, 2024 at 9:27 AM Ed Behn <ed@behn.us> wrote:
> Thank you for your guidance. It turns out the call was coming from inside the house. The error isn't caused by
Postgres.It's the library that I'm using that reported the error. My extension passes any errors it generates as
PostgresERRORs.
Yeah, I was kind of wondering if it was something like that. But I
figured it was a capital mistake to theorize in advance of the data.
Glad you figured it out.
--
Robert Haas
EDB: http://www.enterprisedb.com