Custom Query (196 matches)

MySQL supports ​two major replication formats: statement-based, where the query is logged and replayed, and row-based, where the changed data is logged and replayed. Statement-based is much older and presumed more stable, and the default in 5.x; ​row-based handles a couple of nondeterministic queries that statement-based replication can't. MySQL 5.1.8 also introduced ​mixed-format logging, which uses statement-based replication where it can and row-based where necessary. 5.1.12 made mixed replication the default, until it was ​reverted in 5.1.29 on the grounds that 5.1 should be compatible with 5.0. We should decide on our own whether we want to use mixed replication (I think there's no compelling need to switch to row-based replication for everything). Among other obvious benefits, more reliable replication means that backups are more likely to match what you see on the primary.

Relatedly, MySQL used to permit users to set a session variable, ​`binlog_format`, to switch logging types for the duration of that session. However, this ability was ​restricted to users with the SUPER privilege (which has always been required for setting that as a _global_ variable), because someone claimed that DBAs might write code that required row-based replication and didn't want a mere user to be able to switch to statement-based replication and foil the DBA's plans. While I question the validity of such a possibility, we certainly don't have DBAs, so it might be worth locally reverting that patch so that users and applications have the option of switching to row-based replication if they prefer it. This would be especially important if we go through autoinstalled apps to see what, if anything, wouldn't work properly statement-based replication.

Anders wrote a while ago:

I talked with presbrey on Monday about his r403 (make suexec pass through PYTHONPATH and PERL5LIB), which I reverted for security concerns. The goal is to make it easier to use locally installed Python or Perl libraries, without having to mess with sys.path or @INC in every script. We came up with one possible solution, which is to have suexec pass PYTHONPATH and PERL5LIB after sanitizing them to make sure they only point to paths in the user's locker.

I came up with an alternative solution for Python that involves significantly less work: I put the line

import site, os.path; site.addsitedir(os.path.expanduser("~/lib/python2.5/site-packages"))

in /usr/lib/python2.5/site-packages/00scripts-home.pth. ecprice and I are going to try out this strategy with the HMMT server.

I don't know of a similar mechanism for Perl, though.

Was ​https://help.mit.edu/?q=497718.

Doing this primarily to see if my patches work.