PostgreSQL Design Check Queries

Catalog of PostgreSQL queries for finding information about a PostgreSQL database and its design problems

	Choose collection:
AND	Choose query type:
AND	Choose query reliability:
AND	Choose category:	Queries of this category provide information about overloading of routines.
AND	Choose data source:	From where does the query gets its information?
AND	Enter string:
AND	Has fixing 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.

There are 6 queries.

Seq nr	Name▲	Goal	Type	Data source	Last update	License	...
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	2021-10-25 16:14	MIT License	View
2	Input parameters with the same name have different types	Find named input parameters of routines that have the same name but different type. It could be a mistake or deliberate due to overloading of routines.	Problem detection	INFORMATION_SCHEMA+system catalog base tables	2024-01-24 15:01	MIT License	View
3	Overloading	Make sure that there is genuine overloading instead of duplication or dead code. "In some programming languages, function overloading or method overloading is the ability to create multiple functions of the same name with different implementations." (Wikipedia) In PostgreSQL one can do it automagically by having multiple routines with the same name but different parameters in the same schema.	General	INFORMATION_SCHEMA+system catalog base tables	2021-12-20 11:40	MIT License	View
4	Overloading may cause runtime error	Routines in the same schema that have the same name and that have parameters with different types or different number of parameters are not considered to be in conflict at the creation time. However, if defaults are provided in the definition of parameters, then these routines might be conflict during runtime.	Problem detection	INFORMATION_SCHEMA+system catalog base tables	2021-10-25 16:11	MIT License	View
5	User-defined routines that have the same name as some system-defined routine.	Avoid creating user-defined routines that have the same name as some system-defined routine because it may cause confusion.	Problem detection	INFORMATION_SCHEMA+system catalog base tables	2021-02-25 17:30	MIT License	View
6	Very similar (but not equal) routine names	Find pairs of names of different types of routines that are very similar but not equal.	Problem detection	INFORMATION_SCHEMA+system catalog base tables	2024-11-30 12:09	MIT License	View