Search Postgresql Archives

Re: How to get around this limitation (ALTER DATABASE db SET search_path = ...)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 1, 2011 at 1:24 PM, David Johnston <polobo@xxxxxxxxx> wrote:
> Hi,
>
>
>
> From the documentation:
>
> “Whenever a new session is subsequently started in that database, the
> specified value becomes the session default value.”
>
> Is there some way to get existing sessions to see the new search_path
> without forcing them to reconnect.

Think about what you're asking.  Imagine you're in the middle of a
transaction using one search path, and suddenly, mid transaction it
just changes.  I don't think you can force it without killing off the
backend the other user's are attached to and forcing them to
reconnect.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux