Thread: BUG #17715: dumps file raise an error on restore if a materialized view use a function calling another function

The following bug has been logged on the website:

Bug reference:      17715
Logged by:          Benoît Fontaine
Email address:      benoitfontaine.ba@gmail.com
PostgreSQL version: 14.5
Operating system:   debian
Description:

## Steps to reproduce :
1- Execute this code on an empty database :
```sql
CREATE FUNCTION square (p integer) RETURNS integer AS $$
BEGIN
    RETURN p * p;
END;
$$ LANGUAGE plpgsql;

CREATE FUNCTION myfunc (p integer) RETURNS integer AS $$
BEGIN
    RETURN square(p) + 1;
END;
$$ LANGUAGE plpgsql;

CREATE TABLE dewey (num integer);

INSERT INTO dewey VALUES (10);

CREATE MATERIALIZED VIEW myview AS (SELECT myfunc (num) FROM dewey);
```
2- Dump this database
3- Restore the dump into another empty database

## Issue
```
psql:res.sql:89: ERROR:  function square(integer) does not exist
LINE 1: square (p) + 1
        ^
HINT:  No function matches the given name and argument types. You might need
to add explicit type casts.
QUERY:  square (p) + 1
CONTEXT:  PL/pgSQL function public.myfunc(integer) line 3 at RETURN
```


On Mon, Dec 12, 2022, 09:28 PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17715
Logged by:          Benoît Fontaine
Email address:      benoitfontaine.ba@gmail.com
PostgreSQL version: 14.5
Operating system:   debian
Description:       

CREATE FUNCTION myfunc (p integer) RETURNS integer AS $$
BEGIN
    RETURN square(p) + 1;
END;
$$ LANGUAGE plpgsql;

Schema qualify the function call so it can work regardless of the search_path setting.

David J.