It will be available as 6.1. We are in the process of trying to make the CE and EE a part of the same binary package. ETA is in a few months. Of course I can't make any promises, etc.

K is a hard guarantee.

K=2 means: *any* two nodes may fail but your cluster will remain up. As long as the *wrong* nodes dont' fail and more than half the nodes are still available the cluster will also remain up

Vertica internally runs most of its threads at a lower priority (higher nice value) Specifically, Vertica runs its query executor threads with a slightly lower priority than its main communications dispatch loop (note that without being root, a process can not increase the priority of a thread). Thi...

Here is some engineering perspective: The load_streams table (now) contains data on both ongoing loads and historical loads -- but the underlying mechanism for the historical data is not particularly optimized and can be big. on 6.0 , If you want a faster way to get access to the information in load...

You can see them all with this command:

select show_all_vertica_options();

Some of them are quite dangerous and can cause database corruption or worse.

Happy poking,
Andrew

I would be happy to incorporate this code into our github extensions repository (https://github.com/vertica/Vertica-Extension-Packages) For legal reasons, I can not include it unless you sign a contributor license agreement, which is straightforward and easy to do: Quoting from: https://github.com/v...

Look at dc_session_starts and dc_session_ends For example: alamb=> select * from dc_session_starts limit 1; time | node_name | session_id | user_id | user_name | client_hostname | client_pid | client_label | client_version | ssl_state | authentication_method | is_internal | session_type ------------...