From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump and search_path |
Date: | 2019-07-09 06:54:25 |
Message-ID: | fb97c1ee-71c6-f513-1345-e894c8d66547@lucee.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 7/8/2019 11:48 PM, Igal @ Lucee.org wrote:
>
> I have a custom search_path:
>
> # show search_path;
> search_path
> ----------------------------------
> "staging, transient, pg_catalog"
> (1 row)
>
> I ran `pg_dump --schema-only` and the only reference in the output to
> search_path is:
>
> SELECT pg_catalog.set_config('search_path', '', false);
>
> Then one of my functions which does not reference the full name of a
> table with its schema fails with "relation [rel-name] does not exist".
>
> Is that a bug? I have seen some old posts about this issue but am not
> sure if there is a ticket or why it still is an issue.
>
Looks like this might be by design. I will follow the links at
https://www.postgresql.org/message-id/flat/MWHPR14MB160079A6D9DC64A2F60E9004C0D00%40MWHPR14MB1600.namprd14.prod.outlook.com
and ask more questions if I have them.
I might need to add the schema name to the table in my function.
Igal
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2019-07-09 07:22:14 | Re: pg_dump and search_path |
Previous Message | Igal @ Lucee.org | 2019-07-09 06:48:25 | pg_dump and search_path |