Is there a way to disable function overloading in Postgres

by

Erwin sent a correct reply. My next reply is related to possibility to disable overloading.

It is not possible to disable overloading – this is a base feature of PostgreSQL function API system – and cannot be disabled. We know so there are some side effects like strong function signature rigidity – but it is protection against some unpleasant side effects when function is used in Views, table definitions, .. So you cannot to disable it.

You can simply check if you have or have not overloaded functions:

postgres=# select count(*), proname 
               from pg_proc 
              where pronamespace <> 11 
              group by proname 
              having count(*) > 1;
 count | proname 
-------+---------
(0 rows)

More Related Contents:

  1. Convert hex in text representation to decimal number
  2. How to convert primary key from integer to serial?
  3. How to set value of composite variable field using dynamic SQL
  4. No function matches the given name and argument types
  5. What are ‘$$’ used for in PL/pgSQL
  6. The forgotten assignment operator “=” and the commonplace “:=”
  7. Truncating all tables in a Postgres database
  8. Making sense of Postgres row sizes
  9. PostgreSQL: ERROR: 42601: a column definition list is required for functions returning “record”
  10. Return multiple fields as a record in PostgreSQL with PL/pgSQL
  11. How do I do large non-blocking updates in PostgreSQL?
  12. Execute a dynamic crosstab query
  13. Generate series of dates – using date type as input
  14. Refresh a materialized view automatically using a rule or notify
  15. Casting NULL type when updating multiple rows
  16. Dynamic SQL (EXECUTE) as condition for IF statement
  17. Returning from a function with OUT parameter
  18. Error when setting n_distinct using a plpgsql variable
  19. Difference between timestamps with/without time zone in PostgreSQL
  20. Postgres FOR LOOP
  21. Dynamic pivot query using PostgreSQL 9.3
  22. Function to loop through and select data from multiple tables
  23. PL/pgSQL functions: How to return a normal table with multiple columns using an execute statement
  24. Change type of varchar field to integer: “cannot be cast automatically to type integer”
  25. SQL Sub queries in check constraint
  26. Cursor based records in PostgreSQL
  27. Select from a table variable
  28. Hashing a String to a Numeric Value in PostgreSQL
  29. plpgsql error “RETURN NEXT cannot have a parameter in function with OUT parameters” in table-returning function
  30. Format specifier for integer variables in format() for EXECUTE?

Leave a Comment