On 2/5/08, Jan S Berg <Jan.Berg at sun.com> wrote: > Hi, > > we have made a draft ARC case for integrating 64bit MySQL and the ODBC > and JDBC Connectors to OpenSolaris: > > http://wikis.sun.com/display/WebStack/MySQL64bitARC > > Please review and comment
I thought that it was now usual to supply 64-bit files in the same package as 32-bit files, rather than creating a separate package? Should the bin directory contain both 32 and 64-bit subdirectories and select the optimal binary using isaexec? (I don't know the answer, I'm just throwing this one out there.) Why have a separate service for 64-bit? Why not just have one service and either choose the optimal server (either by isaexec as above, or by the method script)? Or maybe an SMF property to select the appropriate binary? I would find it terribly confusing to have different services. Likewise, why have a different location for the data files? (A technical question - are the data files incompatible between 32 and 64 bit servers?) Certainly on x64, I *always* run mysql servers in 64-bit, as the performance boost is noticeable - I haven't noticed much difference on sparc. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
