Re: How to get around this limitation (ALTER DATABASE db SET search_path = ...) - Mailing list pgsql-general

From Scott Marlowe
Subject Re: How to get around this limitation (ALTER DATABASE db SET search_path = ...)
Date
Msg-id CAOR=d=2mPfp5ZuWLBm98qEu5Wj+sseGwUTpfHd5ZppeC+i8S7w@mail.gmail.com
Whole thread Raw
In response to How to get around this limitation (ALTER DATABASE db SET search_path = ...)  ("David Johnston" <polobo@yahoo.com>)
List pgsql-general
On Thu, Sep 1, 2011 at 1:24 PM, David Johnston <polobo@yahoo.com> 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.

pgsql-general by date:

Previous
From: Rory Campbell-Lange
Date:
Subject: UPDATE using query; per-row function calling problem
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade from 8.3.4 issue