Performance of IN clause with Binary values



I was told that when using an IN clause with binary values, Vertica splits the IN statement into an equivalent number of OR statements behind the scene.  Is this correct?  If so, then doing so with a large number of values affects the query running time.  Is there a way to address this performance?



Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file