News for hackers. Stuff that matters.

A comment on Spotify excessively writing to drive. Parent comment

Re:Spotify excessively writing to drive by joemi on Wednesday November 09, 2016 @06:07PM (#12915759)
Does anyone know why "xxxxxx;"? Seems like that would make an invalid call, so wouldn't it make more sense to replace it with some sort of no-op? Or is xxxxxx sql's way of doing a no-op?
[ Parent | on HN ]
Re:Spotify excessively writing to drive by CGamesPlay on Wednesday November 09, 2016 @08:27PM (#12916830)
Because that breaks the statement, Spotify doesn't care if this particular statement succeeds or fails, and because it has the same length as "VACUUM;". Since this is being modified in a binary, you can't change the length of the string, or else you'll overwrite some other part of the data.
[ Parent | on HN ]
Re:Spotify excessively writing to drive by jleahy on Wednesday November 09, 2016 @06:54PM (#12916191)
Presumably it results in an error, but if the return value isn't checked then that's fine.
[ Parent | on HN ]
Re:Spotify excessively writing to drive by pbhjpbhj on Wednesday November 09, 2016 @08:02PM (#12916682)
DO 0

or

SET @noop=0

or

NULL; -- works in pg at least

seem like good possibilities.

[ Parent | on HN ]