Re: [HACKERS] "SET search_path" clause ignored during function creation

From: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Erwin Brandstetter <brsaweda(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] "SET search_path" clause ignored during function creation
Date: 2010-05-11 04:59:00
Message-ID: 20100511135859.D618.52131E4D@oss.ntt.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers


Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> > Thanks for the report! Please check whether the attached patch
> > is the correct fix. An additional regression test is included.
>
> That's going to provoke "uninitialized variable" compiler warnings,
> but otherwise it seems reasonably sane.

I applied a revised version that can surpress compiler warnings
to 9.0beta, 8.4 and 8.3.

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Chana Slutzkin 2010-05-11 07:21:07 BUG #5457: dblink_connect now restricts non-superusers to password
Previous Message Robert Haas 2010-05-10 22:32:42 Re: BUG #5448: psql \set does not terminate if variable is referenced recursively

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2010-05-11 05:01:23 Re: max_standby_delay considered harmful
Previous Message Fujii Masao 2010-05-11 04:37:53 Re: Make archiver check for SIGHUP more often?