| From: | Casey Allen Shobe <casey(at)shobe(dot)info> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)mail(dot)com>, Rodrigo Rosenfeld Rosas <rr(dot)rosas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: wrong search_path being used |
| Date: | 2013-01-14 18:04:45 |
| Message-ID: | CAFmVg3hYCgrBmiLC937VfGUHjbME72_FQChaxO1Sq9+Z1jZniQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Just adding in my two cents...
At my last company we had several hundred stored procedures which all set a
search path dynamically based on an input argument prior to running any
queries. The current behavior is very alarming and challenging to
consistently workaround.
Would be very happy to see a future version without the search path
catching issues.
Cheers,
--
Casey Allen Shobe
casey(at)shobe(dot)info
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2013-01-14 18:07:29 | Re: BUG #7807: "sign" function returns double |
| Previous Message | a_rares | 2013-01-14 14:21:08 | BUG #7807: "sign" function returns double |