Re: "SET search_path" clause ignored during function creation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Erwin Brandstetter <brsaweda(at)gmail(dot)com>, 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 17:56:54
Message-ID: 13586.1273514214@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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 don't particularly see the point of the added regression test.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2010-05-10 22:32:42 Re: BUG #5448: psql \set does not terminate if variable is referenced recursively
Previous Message Bryan Henderson 2010-05-10 16:16:32 Re: bool: symbol name collision

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2010-05-10 18:42:57 Re: no universally correct setting for fsync
Previous Message Greg Stark 2010-05-10 17:46:53 Re: no universally correct setting for fsync