Releases: okbob/plpgsql_check
Releases · okbob/plpgsql_check
2.8.11
18 Feb 13:50
Compare
Sorry, something went wrong.
No results found
fix meson build for pg 14 and pg 15
2.8.10
18 Feb 05:07
Compare
Sorry, something went wrong.
No results found
allow to run regress tests on server with active pg_stat_statements
correct call post_parse_analyze_hook (nobody reported)
fixing some oversights in code
2.8.9
12 Feb 13:01
Compare
Sorry, something went wrong.
No results found
2.8.8
06 Feb 12:09
Compare
Sorry, something went wrong.
No results found
fix possible crash due usage of currupted memory
Full Changelog : v2.8.7...v2.8.8
2.8.7
05 Feb 07:02
Compare
Sorry, something went wrong.
No results found
fix calling prev_plpgsql_plugin
internal cleaning
2.8.6
04 Feb 20:44
Compare
Sorry, something went wrong.
No results found
rewrite pldbgapi - the base of tracker, profiler, .. fmgr API is not used now
raise warning when expression volatility is higher than routine volatility
raise warning when reserved keyword is used as a label
detect obsolete usage SELECT expr INTO var
Full Changelog : v2.8.5...v2.8.6
2.8.5
28 Nov 17:06
Compare
Sorry, something went wrong.
No results found
Previous commit 17073e8 released tracked const (plpgsql) string. It is wrong, because this string can be used more times.
2.8.4
23 Nov 05:00
Compare
Sorry, something went wrong.
No results found
force cast constant strings to target type
2.8.3
11 Oct 04:23
Compare
Sorry, something went wrong.
No results found
fix check if function was already checked or not in passive mode for PostgreSQL 18
fix false alarm about bad number of target variables when procedure has composite inout argument
Full Changelog : v2.8.2...v2.8.3
2.8.2
28 Jul 04:38
Compare
Sorry, something went wrong.
No results found
set correctly context of hiddent cast for all cases (not just for assignment), and for this warning set the query field when the statement is EXECSQL