Re: "Dynamic routing" to different databases - Mailing list pgsql-admin

From Alex Balashov
Subject Re: "Dynamic routing" to different databases
Date
Msg-id 560D4772.4020002@evaristesys.com
Whole thread Raw
In response to Re: "Dynamic routing" to different databases  (Igor Neyman <ineyman@perceptron.com>)
Responses Re: "Dynamic routing" to different databases  ("Nicholson, Brad (Toronto, ON, CA)" <bnicholson@hpe.com>)
List pgsql-admin
On 10/01/2015 09:44 AM, Igor Neyman wrote:

> Why should it " take a lot of code modification"?
> Modifying "search_path" is not enough?

You're right, it's not that big of a deal. I had been under the
impression that

    SET search_path TO schema;

is a psql-level construct, not something that can be embedded in live
queries. So, I was expecting to have to rewrite thousands of lines of
stored procedures to take a schema parameter and construct dynamic query
strings with dynamic table names and so on.

Assuming one can simply do:

    SET search_path TO <schema>; SELECT query_business_as_usual();

I'm in a pretty good place!

--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States

Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/


pgsql-admin by date:

Previous
From: Igor Neyman
Date:
Subject: Re: "Dynamic routing" to different databases
Next
From: "Nicholson, Brad (Toronto, ON, CA)"
Date:
Subject: Re: "Dynamic routing" to different databases