Filter Queries

Found 6 queries.

  • All the queries about database objects contain a subcondition to exclude from the result information about the system catalog.
  • Although the statements use SQL constructs (common table expressions; NOT in subqueries) that could cause performance problems in case of large datasets it shouldn't be a problem in case of relatively small amount of data, which is in the system catalog of a database.
  • Statistics about the catalog content and project home in GitHub that has additional information.

#1. Do not create user-defined routines that have the same name as some installed extension routine

INFORMATION_SCHEMA+system catalog base tables

Avoid creating user-defined routines that have the same name as some extension routine because it may cause confusion.

Problem detection License: MIT (opens in new tab)

#2. Extension routines

system catalog base tables only

Find all routines that belong to an extension.

General License: MIT (opens in new tab)

#3. Extension routines in the schema "public"

system catalog base tables only

Find extensions that routines are in the schema public.

Problem detection License: MIT (opens in new tab)

#4. Extension routines that execution privilege has been granted to PUBLIC

INFORMATION_SCHEMA+system catalog base tables

Know the privileges that users have in your system. Probably all the database users do not need these privileges.

Problem detection License: MIT (opens in new tab)

#5. Extensions that are available but are not installed

system catalog base tables only

Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database.

General License: MIT (opens in new tab)

#6. Installed extensions

system catalog base tables only

Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database.

General License: MIT (opens in new tab)
# Name (sorted ascending) Goal Type Data source Last update License Actions
1 Do not create user-defined routines that have the same name as some installed extension routine Avoid creating user-defined routines that have the same name as some extension routine because it may cause confusion. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
2 Extension routines Find all routines that belong to an extension. General system catalog base tables only MIT (opens in new tab) View (opens in new tab)
3 Extension routines in the schema "public" Find extensions that routines are in the schema public. Problem detection system catalog base tables only MIT (opens in new tab) View (opens in new tab)
4 Extension routines that execution privilege has been granted to PUBLIC Know the privileges that users have in your system. Probably all the database users do not need these privileges. Problem detection INFORMATION_SCHEMA+system catalog base tables MIT (opens in new tab) View (opens in new tab)
5 Extensions that are available but are not installed Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database. General system catalog base tables only MIT (opens in new tab) View (opens in new tab)
6 Installed extensions Try to use as much the possibilities of the DBMS as possible. On the other hand, do not install extensions that are not needed in order not to overcomplicate the database. General system catalog base tables only MIT (opens in new tab) View (opens in new tab)