postgresql_instances

Overview

Name	postgresql_instances
Type	Resource
Id	linode.databases.postgresql_instances

Fields

Name	Datatype	Description
id	integer	A unique ID that can be used to identify and reference the Managed Database.
allow_list	array	A list of IP addresses that can access the Managed Database. Each item can be a single IP address or a range in CIDR format. By default, this is an empty array ([]), which blocks all connections (both public and private) to the Managed Database. If 0.0.0.0/0 is a value in this list, then all IP addresses can access the Managed Database.
cluster_size	integer	The number of Linode Instance nodes deployed to the Managed Database. Choosing 3 nodes creates a high availability cluster consisting of 1 primary node and 2 replica nodes.
created	string	When this Managed Database was created.
encrypted	boolean	Whether the Managed Databases is encrypted.
engine	string	The Managed Database engine type.
hosts	object	The primary and secondary hosts for the Managed Database. These are assigned after provisioning is complete.
label	string	A unique, user-defined string referring to the Managed Database.
port	integer	The access port for this Managed Database.
region	string	The Region ID for the Managed Database.
replication_commit_type	string	The synchronization level of the replicating server. Must be local or off for the asynch replication type. Must be on, remote_write, or remote_apply for the semi_synch replication type.
replication_type	string	The replication method used for the Managed Database. Defaults to none for a single cluster and semi_synch for a high availability cluster. Must be none for a single node cluster. Must be asynch or semi_synch for a high availability cluster.
ssl_connection	boolean	Whether to require SSL credentials to establish a connection to the Managed Database. Use the Managed PostgreSQL Database Credentials View (GET /databases/postgresql/instances/{instanceId}/credentials) command for access information.
status	string	The operating status of the Managed Database.
type	string	The Linode Instance type used by the Managed Database for its nodes.
updated	string	When this Managed Database was last updated.
updates	object	Configuration settings for automated patch update maintenance for the Managed Database.
version	string	The Managed Database engine version.

Methods

Name	Accessible by	Required Params	Description
getDatabasesPostgreSQLInstance	SELECT	instanceId	Display information for a single, accessible Managed PostgreSQL Database.
getDatabasesPostgreSQLInstances	SELECT		Display all accessible Managed PostgreSQL Databases.
deleteDatabasesPostgreSQLInstance	DELETE	instanceId	Remove a Managed PostgreSQL Database from your Account. Requires read_write access to the Database. The Database must have an active, failed, or degraded status to perform this command. Only unrestricted Users can access this command, and have access regardless of the acting token's OAuth scopes.
_getDatabasesPostgreSQLInstance	EXEC	instanceId	Display information for a single, accessible Managed PostgreSQL Database.
_getDatabasesPostgreSQLInstances	EXEC		Display all accessible Managed PostgreSQL Databases.
postDatabasesPostgreSQLInstancePatch	EXEC	instanceId	Apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database. This function runs during regular maintenance windows, which are configurable with the Managed PostgreSQL Database Update (PUT /databases/postgresql/instances/{instanceId}) command. Requires read_write access to the Database. The Database must have an active status to perform this command. Note If your database cluster is configured with a single node, you will experience downtime during this maintenance. Consider upgrading to a high availability plan to avoid any downtime due to maintenance. The database software is not updated automatically. To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.
postDatabasesPostgreSQLInstances	EXEC	data__engine, data__label, data__region, data__type	Provision a Managed PostgreSQL Database. Restricted Users must have the add_databases grant to use this command. New instances can take approximately 15 to 30 minutes to provision. The allow_list is used to control access to the Managed Database. IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. If 0.0.0.0/0 is a value in this list, then all IP addresses can access the Managed Database. Entering an empty array ([]) blocks all connections (both public and private) to the Managed Database. All Managed Databases include automatic, daily backups. Up to seven backups are automatically stored for each Managed Database, providing restore points for each day of the past week. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database during configurable maintenance windows. If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. The database software is not updated automatically. To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one. To modify update the maintenance window for a Database, use the Managed PostgreSQL Database Update (PUT /databases/postgresql/instances/{instanceId}) command.
putDatabasesPostgreSQLInstance	EXEC	instanceId	Update a Managed PostgreSQL Database. Requires read_write access to the Database. The Database must have an active status to perform this command. Updating addresses in the allow_list overwrites any existing addresses. IP addresses and ranges in this list can access the Managed Database. All other sources are blocked. If 0.0.0.0/0 is a value in this list, then all IP addresses can access the Managed Database. Entering an empty array ([]) blocks all connections (both public and private) to the Managed Database. Note: Updates to the allow_list may take a short period of time to complete, making this command inappropriate for rapid successive updates to this property. All Managed Databases include automatic patch updates, which apply security patches and updates to the underlying operating system of the Managed PostgreSQL Database. The maintenance window for these updates is configured with the Managed Database's updates property. If your database cluster is configured with a single node, you will experience downtime during this maintenance window when any updates occur. It's recommended that you adjust this window to match a time that will be the least disruptive for your application and users. You may also want to consider upgrading to a high availability plan to avoid any downtime due to maintenance. The database software is not updated automatically. To upgrade to a new database engine version, consider deploying a new Managed Database with your preferred version. You can then migrate your databases from the original Managed Database cluster to the new one.