| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | stan <stanb(at)panix(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: A very puzzling backup/restore problem |
| Date: | 2019-10-24 22:11:40 |
| Message-ID: | 12087.1571955100@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 10/24/19 2:58 PM, stan wrote:
>> So, it appears that this means that the function cannot be found, even if it is in the new
>> (default) schema.
> The original error was not about finding the function it was about not
> finding the table in the function:
> psql:task_instance.dump:55: ERROR: relation "permitted_work" does not exist
> LINE 3: permitted_work
> ^
> You need to schema qualify the table name inside the function.
Or attach a SET clause to the function, so that it executes with a
known search_path regardless of the session's prevailing path.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2019-10-24 23:31:39 | Re: EXPLAIN BUFFERS and I/O timing accounting questions |
| Previous Message | Adrian Klaver | 2019-10-24 22:02:39 | Re: A very puzzling backup/restore problem |