Wed May 4 12:27:56 PDT 2011
- Previous message: [Slony1-bugs] [Bug 178] More sophisticated FAILOVER
- Next message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=203 Summary: Use of "name" type conflicts with pg_upgrade Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: core scripts AssignedTo: slony1-bugs at lists.slony.info ReportedBy: cbbrowne at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 Various columns in the Slony schema that store relation names use the "name" type. According to PostgreSQL docs: http://www.postgresql.org/docs/9.0/static/datatype-character.html "The name type exists only for the storage of identifiers in the internal system catalogs and is not intended for use by the general user. Its length is currently defined as 64 bytes (63 usable characters plus terminator) but should be referenced using the constant NAMEDATALEN in C source code." There is some room to quibble over whether Slony is an "internal system" thing or a "general user," but it has been observed that the use of the name type adversely affects attempts to run pg_upgrade against Slony nodes. http://lists.slony.info/pipermail/slony1-general/2011-April/011620.html It seems as though we should switch from "name" to "text". -- 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 178] More sophisticated FAILOVER
- Next message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list