From: Alex Balashov <abalashov@evaristesys.com>
To: pgsql-admin@postgresql.org
Subject: Re: "Dynamic routing" to different databases
Date: Thu, 1 Oct 2015 10:47:14 -0400
Message-ID: <560D4772.4020002@evaristesys.com> (raw)
In-Reply-To: <A76B25F2823E954C9E45E32FA49D70ECCD54D23C@mail.corp.perceptron.com>
References: <560BFE58.9030201@evaristesys.com>
<560C6F2D.1090107@evaristesys.com>
<A76B25F2823E954C9E45E32FA49D70ECCD54D23C@mail.corp.perceptron.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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/
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: abalashov@evaristesys.com
Subject: Re: "Dynamic routing" to different databases
In-Reply-To: <560D4772.4020002@evaristesys.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox