You can limit maximum client session on the database level. But I don't think there is any feature to allow number of client sessions for a particular user.
Check this link. A workaround ( i have not tried it to see whether it works well) is to set up a resource pool for the restricted user and set a maxconcurrency cap on the pool. Memory can be set via maxmemorysize with a memorysize of 0 to avoid setting memory aside for this occasional user. This feature could also be used to limit a set of users to a number of running queries ( not sessions)
Comments
You can limit maximum client session on the database level.
But I don't think there is any feature to allow number of client sessions for a particular user.
This will be a good feature to add.
Hope this helps.
NC
http://my.vertica.com/docs/7.1.x/HTML/index.htm#Authoring/AdministratorsGuide/ResourceManager/Scenar...