| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: search_path vs extensions |
| Date: | 2009-05-28 18:37:01 |
| Message-ID: | 4A1ED9CD.7040401@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/28/09 12:36 AM, Dimitri Fontaine wrote:
> That really seems exactly to be what we're proposing with pre_ and post_
> search_path components: don't change current meaning of search_path,
> just give DBAs better ways to manage it. And now that you're leaning
> towards a search_path suffix, don't you want a prefix too?
Yeah, I thought about a prefix, but I couldn't come up with a way it
would be useful, and I could come up with a lot of scenarios where it
would be a big foot-gun.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-05-28 18:38:29 | Re: search_path vs extensions |
| Previous Message | Greg Stark | 2009-05-28 18:27:01 | Re: search_path vs extensions |