Skip to content

please support ranges in custom_query (or generally) #192

Description

@justinpryzby

For example, I'd like to be able to do this, rather than implement the comparison in a shellscript, as I've done.

check_postgres --action custom_query -w 140000:150000 --query "SELECT current_setting('server_version_num') AS result"
ERROR: Invalid argument for 'warning' option: must be an integer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions