Releases: okbob/plpgsql_check
Releases · okbob/plpgsql_check
2.7.1
21 Dec 05:35
Compare
Sorry, something went wrong.
No results found
fix missing invalidation of traced constant when SELECT INTO command is used
add pragmas for better check of identifiers used by dynamic SQL (assert-schema, assert-table, assert-column)
2.7.0
06 Dec 06:47
Compare
Sorry, something went wrong.
No results found
possibility to detect unclosed cursors (runtime)
2.6.2
23 Nov 17:07
Compare
Sorry, something went wrong.
No results found
fix crash when argument of EXECUTE is empty string (it is allowed possibility)
fix crash when the checked plan is not valid (now, the invalid plan is replaned)
tracer shows transaction nesting level (increased by using subtransactions)
tracer can show number of subxids up to 64 (after this value there can be significant slowdown)
2.6.1
03 Nov 06:53
Compare
Sorry, something went wrong.
No results found
fix crash when SRF function is used in expression
2.6.0
31 Oct 13:51
Compare
Sorry, something went wrong.
No results found
add new option constants_tracing (true by default) for controling of possibility to trace constants
2.5.4
12 Oct 18:54
Compare
Sorry, something went wrong.
No results found
fix usage of prev_needs_fmgr_hook
warning when tracer is activated, but it is not enabled by superuser
2.5.3
04 Oct 06:37
Compare
Sorry, something went wrong.
No results found
fix pldbgapi2 to correctly process empty exception handler
2.5.2
29 Sep 18:02
Compare
Sorry, something went wrong.
No results found
allows to install plpgsql_check from plpgsql
2.5.1
14 Sep 05:18
Compare
Sorry, something went wrong.
No results found
fix collision of global variable names with global variables from pglogical extension
2.5.0
08 Sep 06:47
Compare
Sorry, something went wrong.
No results found
change signature of profiler/tracer control functions
fix issues #149 , #150 in profiler