From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4860: Indexes gone after restore |
Date: | 2009-06-18 18:43:58 |
Message-ID: | 13528.1245350638@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov> writes:
> If you have an index on a function that calls another function where the function being called does not have the namespace specifically prefixed.
This has nothing to do with either indexes or pg_dump. A function that
calls another function, or references a table, or does much of anything
at all with other database objects, is responsible for schema-qualifying
those references if it expects to be callable with random settings of
search_path.
In some cases the most practical way to do this is to attach a "SET
search_path" option to the function rather than change its source code.
But in either case it's ultimately the function author's responsibility.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Ryabov | 2009-06-18 21:30:05 | BUG #4861: Incorrect log_line_prefix default value in postgresql.conf |
Previous Message | Obe, Regina | 2009-06-18 18:33:39 | Re: BUG #4860: Indexes gone after restore |