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

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: David Johnston <polobo(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to get around this limitation (ALTER DATABASE db SET search_path = ...)
Date: 2011-09-01 20:41:13
Message-ID: CAOR=d=2mPfp5ZuWLBm98qEu5Wj+sseGwUTpfHd5ZppeC+i8S7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 1, 2011 at 1:24 PM, David Johnston <polobo(at)yahoo(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2011-09-01 20:42:51 Re: Why schema of table is removed from explain?
Previous Message Tom Lane 2011-09-01 20:39:06 Re: Why schema of table is removed from explain?