The format is name=number, with different items separated by colons or semicolons (or any other symbol). Valid lock names are ‘total’, ‘waiting’, or the name of a lock type used by Postgres. These names are case-insensitive and do not need the “lock” part on the end, so exclusive will match ‘ExclusiveLock’. The –warning and –critical options can be specified as simple numbers, which represent the total number of locks, or they can be broken down by type of lock.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
The name of a file system can be filtered when using the disk_space action. The name of a relation can be filtered when using the following actions: bloat, index_size, table_size, relation_size, last_vacuum, last_autovacuum, last_analyze, and last_autoanalyze. The name of a setting can be filtered when using the settings_checksum action. The options –include and –exclude can be combined to limit which things are checked, depending on the action. The name of the database can be filtered when using the following actions: backends, database_size, locks, query_time, txn_idle, and txn_time.
In sum, a control variable now always has a displayable value that reflects what psql is actually doing. unset on a special variable now explicitly sets the variable to its default value, which is also the value it acquires at startup. As a special exception, set with an empty or omitted new value, on a boolean-valued special variable, still has the effect of setting the variable to on; but now it actually acquires that value rather than an empty string. Previously, setting one of psql ‘s special variables to an invalid value silently resulted in the default behavior. set on a special variable now fails if the proposed new value is invalid.
No other output is supported, as the output is informational and does not lend itself to alerts, such as used with Nagios. (symlink: check_postgres_dbstats) Reports information from the pg_stat_database view, and outputs it in a Cacti-friendly manner. If no options are given, all databases are returned, one per line. You can include a specific database by use of the –include option, or you can use the –dbname option.
If a major upgrade is available, a warning is returned. The current version is obtained by running boxinfo. (symlink: check_postgres_new_version_box) Checks if a newer version of the boxinfo program is available. See also the information on the –get_method option. If a revision upgrade is available, a critical is returned. (boxinfo is a program for grabbing important information from a server and putting it into a HTML format: see http://bucardo. Org/wiki/boxinfo for more information).
The new SQL function brin_summarize_range() updates BRIN index summarization for a specified range and brin_desummarize_range() removes it. This is helpful to update summarization of a range that is now smaller due to UPDATEs and DELETEs.
Word), with optional parens at the end. (symlink: check_postgres_query_runtime) Checks how long a specific query takes to run, by executing a “EXPLAIN ANALYZE” against it. It must consist of a single word (or schema. The –warning and –critical options are the maximum amount of time the query should take. The name of the view or function to be run must be passed in to the –queryname option. If no units are given, ‘seconds’ are assumed. Valid units are seconds, minutes, and hours; any can be abbreviated to the first letter. Both the warning and the critical option must be given.
If either option is not given, the default values of 1. For a more detailed discussion of what this number represents and what to do about it, please visit the page http://www. The –warning and –critical options indicate the number of transactions done, and must be a positive integer. (symlink: check_postgres_txn_wraparound) Checks how close to transaction wraparound one or more databases are getting. 4 billion are used. There is no need to run this command more than once per database cluster.
Connect as port 5432 on the first two hosts, and as port 5433 on the third one. Example 4: Check all databases except those with “test” in their name, but allow ones that are named “pg_greatest”. We want to always throw a critical when we reach 30 or more connections.
The first time this is run a snapshot of all the items in the database is saved to a local file. When you run it again, that snapshot is read in and becomes “database #2” and is compared to the current database. If only a single host is given, it is assumed we are doing a “time-based” report.
` /opt/supermarket/embedded/bin/pg_dump -c -f ` `.