plpgsql_check

plpgsql_check is a linter tool (does source code static analyze) for the PostgreSQL language plpgsql (the native language for PostgreSQL store procedures).

OTHER License

Stars
630
Committers
16

Bot releases are visible (Hide)

plpgsql_check - 2.7.10

Published by okbob about 1 month ago

  • fix another crash related unexpected order of fmgr hook calls
plpgsql_check - 2.7.9 Latest Release

Published by okbob about 2 months ago

  • fix crash in profiler when parameter of EXECUTE is empty string
plpgsql_check - 2.7.8

Published by okbob 3 months ago

  • fix crash when plpgsql_check is used on anonymous code block
plpgsql_check - 2.7.7

Published by okbob 4 months ago

fix possibly crash when a plan is created by plpgsql, then plancache
is invalidated (due sinval), and same plan is created by plpgsql_check
in passive mode.

plpgsql_check - 2.7.6

Published by okbob 5 months ago

  • fix crash when pragma assert-column is not correctly used
plpgsql_check - 2.7.5

Published by okbob 7 months ago

  • fix crash related to active cursor leak detection and ending transaction inside procedure
plpgsql_check - 2.7.4

Published by okbob 7 months ago

  • fix another crash related to constant tracing
plpgsql_check - 2.7.3

Published by okbob 8 months ago

  • fix false alarm related to bug in trace constant in format function (when positional placeholder was used)
plpgsql_check - 2.7.2

Published by okbob 9 months ago

  • fix false alarm of unclosed cursors test
plpgsql_check - 2.7.1

Published by okbob 10 months ago

  • 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)
plpgsql_check - 2.7.0

Published by okbob 11 months ago

  • possibility to detect unclosed cursors (runtime)
plpgsql_check - 2.6.2

Published by okbob 11 months ago

  • 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)
plpgsql_check - 2.6.1

Published by okbob 12 months ago

  • fix crash when SRF function is used in expression
plpgsql_check - 2.6.0

Published by okbob 12 months ago

  • add new option constants_tracing (true by default) for controling of possibility to trace constants
plpgsql_check - 2.5.4

Published by okbob about 1 year ago

  • fix usage of prev_needs_fmgr_hook
  • warning when tracer is activated, but it is not enabled by superuser
plpgsql_check - 2.5.3

Published by okbob about 1 year ago

  • fix pldbgapi2 to correctly process empty exception handler
plpgsql_check - 2.5.2

Published by okbob about 1 year ago

  • allows to install plpgsql_check from plpgsql
plpgsql_check - 2.5.1

Published by okbob about 1 year ago

  • fix collision of global variable names with global variables from pglogical extension
plpgsql_check - 2.5.0

Published by okbob about 1 year ago

  • change signature of profiler/tracer control functions
  • fix issues #149, #150 in profiler
plpgsql_check - 2.4.0

Published by okbob about 1 year ago

  • remove support for PostgreSQL 10 and 11
  • significant refactoring (code cleaning) of profiler and tracer
  • no new functionality, just code cleaning and remove obsolete code
Package Rankings
Top 8.63% on Alpine-v3.7
Top 9.83% on Alpine-v3.14
Top 9.38% on Alpine-v3.11
Top 11.18% on Alpine-v3.15
Top 8.17% on Proxy.golang.org
Top 9.08% on Alpine-v3.9
Top 9.2% on Alpine-v3.13
Top 9.41% on Alpine-v3.8
Top 10.91% on Alpine-v3.10
Top 11.98% on Alpine-v3.16
Top 13.05% on Alpine-v3.17
Top 9.16% on Alpine-v3.12
Top 6.68% on Alpine-v3.18
Top 10.98% on Alpine-edge
Badges
Extracted from project README
Stand With Ukraine