On Tue, 2008-05-13 at 16:27 -0600, Richard K Miller wrote: > On May 13, 2008, at 4:06 PM, Lonnie Olson wrote: > > > On Tue, 2008-05-13 at 15:10 -0600, Richard K Miller wrote: > >> If MySQL logs to a named pipe, and "no one is there to hear it," does > >> it affect database performance? > > > > It could. mkfifo creates blocking named pipes. Meaning a reader will > > block, and wait for someone else to start writing to it. Also > > vice-versa, the writer will wait for a reader. > > http://developers.sun.com/solaris/articles/named_pipes.html > > > > A blocking log file sounds really bad to me. > > > How bad, and why? > > Is this an acceptable solution for a development machine where > convenience is more important than performance? Is there a better way > to do this?
Imagine mysql trying to write to it's log file, and it is told to wait by the OS indefinitely. MySQL could fill up buffers, hang, or do other bad things. Now on a dev machine this isn't necessarily a big deal. Just remember to leave your tail process running. --lonnie
_______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
