I think for the use case you describe, and given the fact
that it does work in production, your solution simply shows
The Power Of PostgreSQL.
Java tries to be cross-platform, JDBC tries to be
cross-database -- these goals don't seem to lend themselves
to advocating or understanding what one particular database
may have to offer over and above basic SQL for solving a
particular problem.
Karsten
--
