Re: search_path improvements WAS: search_path vs extensions

From: Greg Stark <stark(at)enterprisedb(dot)com>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
Subject: Re: search_path improvements WAS: search_path vs extensions
Date: 2009-05-30 00:16:25
Message-ID: 4136ffa0905291716v76be340fye2714aeb22870de0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 29, 2009 at 11:03 PM, David E. Wheeler <david(at)kineticode(dot)com> wrote:
> On May 29, 2009, at 2:52 PM, Josh Berkus wrote:
>
>> a) the ability to "push" a schema onto the current search path
>> b) the ability to "pull" a schema off the current search path
>
> push, pop, shift, unshift. :-)
>
> Come to think of it, I want these for arrays, too. ;-)

push and unshift sure -- and you do have those for arrays, it's spelled ||.

I'm not so sure about pop/shift though. How would you know the element
you want is at the beginning/end unless you just put it there?

I think what you really want is to use SET LOCAL or RESET to restore
it to whatever it was before you started futzing with it. We might
need a more flexible way to do that that isn't tied to transactions
though.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira de Oliveira 2009-05-30 00:16:49 Re: Clean shutdown and warm standby
Previous Message Greg Stark 2009-05-29 23:53:14 Re: search_path vs extensions