Chapman Flack

I understand. Do you think the problem could be replicable in a PostgreSQL instance with your software but different data, or fake data, or not all your data? I routinely...

Any news?

I'm not sure I've seen enough detail yet to complete the picture, but this explanation changes my understanding somewhat. It had sounded like something that went wrong only on the...

> Not sure I'm clear on what you mean by "expected type"? Java has a notion of _checked_ exceptions, which are not supposed to be raised except by code that...

PL/Java generally reports database errors as subclasses of `java.sql.SQLException`, as it is required to by the JDBC API. The trouble is, that is a _checked_ exception type, so you are...

All of the configuration settings that _can_ be overridden outside of the conf file can already be set by existing PostgreSQL API: see the `SET` and `SHOW` commands and the...

I have added a pull request #535 that should appear when PL/Java 1.6.10 comes out and simplify tracking down this kind of mishandled-exception bug. I don't know if you have...

The new exception-handling and logging features documented in the comment above have landed in 1.6.10.

Hmm. Culprit seems to be postgres/postgres@4d82750. I think probably `get_toast_snapshot()` for the win.

I believe the most recent merged pull request #529 should take care of PG18. A test build from the `REL1_6_STABLE` branch ought to work now. I always have a bit...