Abbas Butt <abbas.b...@enterprisedb.com> writes: > What is happening for me is that PG_RE_THROW takes me to PG_TRY in the same > function and then PG_TRY jumps to PG_CATCH where PG_RE_THROW again jumps to > PG_TRY in the same function resulting in an infinite loop. The query > therefore never returns. It is supposed to throw the error and quit.
Apparently PG_exception_stack isn't getting restored properly, but it's sure hard to see why. I'm suspicious that you have something silly like mismatched braces in the vicinity of the TRY/CATCH structure. FWIW, doing things like disconnecting remote sessions might be better handled in transaction-cleanup logic, anyway. What covers you for that if the query aborts while control is not within your PG_TRY block? regards, tom lane -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers