Thu Dec 9 10:10:03 PST 2010
- Previous message: [Slony1-bugs] [Bug 184] Set search_path for most/all Slony functions?
- Next message: [Slony1-bugs] [Bug 185] New: Function argument cleanup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=184 --- Comment #3 from Steve Singer <ssinger at ca.afilias.info> 2010-12-09 10:10:03 PST --- > If we have Slony functions set search_path at the time that the functions are > defined, then there is no problem with having two slony clusters on the same > database. > > - When functions relating to cluster "_a" are called, search path is set to > "_a", and they get the right objects. > > - When functions relating to cluster "_b" are called, search path is set to > "_b", again, providing the right objects. > > The very same piece of configuration, @NAMESPACE@, is being stored in one of > two places: > > a) In each reference to tables, sequences, views, functions, so if we miss > one, things will break. > > b) In the function's search_path setting. > > We get rid of a bunch of references to @NAMESPACE@ by putting it into the > function definition. I misunderstood your comment. I thought you were taking about setting the search_path IN the function not as a parameter to CREATE FUNCTION. This makes more sense. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 184] Set search_path for most/all Slony functions?
- Next message: [Slony1-bugs] [Bug 185] New: Function argument cleanup
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list