Re: "SET search_path" clause ignored during function creation

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Erwin Brandstetter <brsaweda(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "SET search_path" clause ignored during function creation
Date: 2010-05-10 06:34:19
Message-ID: 20100510153419.9C58.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers


Erwin Brandstetter <brsaweda(at)gmail(dot)com> wrote:

> Function bodies are checked using the _current_ search_path instead of
> the search_path supplied by the "SET search_path" clause.
>
> Proposed solution: Function bodies should be checked with the
> search_path provided by "SET search_path" an _not_ with the current
> search path at the time pof creation.

Thanks for the report! Please check whether the attached patch
is the correct fix. An additional regression test is included.

Regards,
---
Takahiro Itagaki
NTT Open Source Software Center

Attachment Content-Type Size
create_function_with_search_path.patch application/octet-stream 2.8 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2010-05-10 12:39:13 Re: bool: symbol name collision
Previous Message Takahiro Itagaki 2010-05-10 03:14:15 Re: BUG #5450: system lacked sufficient buffer space, or because a queue was full, could not perform the operation

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-05-10 08:01:57 Re: max_standby_delay considered harmful
Previous Message Simon Riggs 2010-05-10 06:27:44 Re: max_standby_delay considered harmful