Thu Nov 29 12:01:16 PST 2007
- Previous message: [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name
- Next message: [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=15 --- Comment #3 from Christopher Browne <cbbrowne at ca.afilias.info> 2007-11-29 12:01:16 --- Got a patch; when I attempt to create a cluster with a wacky-long cluster name, set initialization blows up as follows, with this reasonably explanatory error message: <stdin>:2: PGRES_FATAL_ERROR select "_slony_regress1_7890123456789012345678901234567890102345".storeSet_int(1, 1, 'All test1 tables'); - ERROR: Length of proposed index name [79] > max_identifier_length [63] - cluster name probably too long CONTEXT: SQL statement "SELECT "_slony_regress1_7890123456789012345678901234567890102345".addPartialLogIndices()" PL/pgSQL function "storeset_int" line 31 at PERFORM -- 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.
- Previous message: [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name
- Next message: [Slony1-bugs] [Bug 15] Set up some form of constraint on length of cluster name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list