The Scaleway Elements Database service allows you to create managed database instances, enabling you to focus on development, configuration or fine-tuning of the database engine, rather than administration.
Scaleway Elements Database manages:
Scaleway Elements Database currently supports PostgreSQL 9.6, 10, and 11.
Support for MySQL will be available soon.
On the details page of your instance, the IP address and your instance’s port are shown.
It is possible to connect to your instance from any application using this IP address and the login/password of any valid database user. This can be managed from the “users” tab.
You can upgrade your database engine version to the next minor release from the management console. A major version upgrade requires your instance’s migration. During the failover to the new version, a short downtime of the instance occurs.
Your instance will not be available during the upgrade to a new version.
Automatic backups are enabled by default. It is possible to disable them at any time in the backup settings of your instance:
To access your Database instance, use the
psql command-line tool with the following command:
psql -h $IP -p $PORT -U $YOUR_USER -d $DATABASE_NAME
You will have to enter your password to establish the connection. The default $DATABASE_NAME to be used is
You can have as many Database Instances as your quota allows. Quotas can be increased by contacting the assistance via support ticket.
Your Database Instance can be partially unavailable during the maintenance window.
pg_extensions are available for Scaleway Elements Database:
|chkpass||data type for auto-encrypted passwords|
|pgrowlocks||show row-level locking information|
|sslinfo||information about SSL certificates|
|citext||data type for case-insensitive character strings|
|tablefunc||functions that manipulate whole tables, including crosstab|
|uuid-ossp||generate universally unique identifiers (UUIDs)|
|pg_buffercache||examine the shared buffer cache|
|intarray||functions, operators, and index support for 1-D arrays of integers|
|bloom||bloom access method - signature file based index|
|hstore||data type for storing sets of (key, value) pairs|
|isn||data types for international product numbering standards|
|dict_int||text search dictionary template for integers|
|tsm_system_rows||TABLESAMPLE method which accepts number of rows as a limit|
|btree_gin||support for indexing common datatypes in GIN|
|plpgsql||PL/pgSQL procedural language|
|tsm_system_time||TABLESAMPLE method which accepts time in milliseconds as a limit|
|unaccent||text search dictionary that removes accents|
|intagg||integer aggregator and enumerator (obsolete)|
|pg_freespacemap||examine the free space map (FSM)|
|pgstattuple||show tuple-level statistics|
|pg_trgm||text similarity measurement and index searching based on trigrams|
|cube||data type for multidimensional cubes|
|dblink||connect to other PostgreSQL databases from within a database|
|fuzzystrmatch||determine similarities and distance between strings|
|earthdistance||calculate great-circle distances on the surface of the Earth|
|dict_xsyn||text search dictionary template for extended synonym processing|
|btree_gist||support for indexing common datatypes in GiST|
|pg_visibility||examine the visibility map (VM) and page-level visibility info|
|ltree||data type for hierarchical tree-like structures|
|pg_prewarm||prewarm relation data|
|postgis||PostGIS geometry, geography, and raster spatial types and functions|
|address_standardizer_data_us||Address Standardizer US dataset example|
|address_standardizer||Used to parse an address into constituent elements. Generally used to support geocoding address normalization step.|
|postgis_sfcgal||PostGIS SFCGAL functions|
|postgis_topology||PostGIS topology spatial types and functions|
|postgis_tiger_geocoder||PostGIS tiger geocoder and reverse geocoder|
If High-Availability (HA) is enabled, fail-over to a healthy node will be done automatically, and your unhealthy node will be auto-healed. If HA is disabled, your instance will be unavailable.
Yes, your instance is available during backup. There will be a performance impact and some actions may not be available.
You can have as many backups as your quota permits. In case you need to increase your quotas, contact our technical assistance by support ticket.
Billing of your Database Instance starts at the moment of its creation and ends at deletion of the resource.
PostgreSQL 9.6, 10 and 11 are currently supported.
MySQL support will come at a later date.
On your behalf, the Scaleway Elements Database Service manages the deployment on Compute ressources, OS, system updates, database engine updates and configuration. High-availability and backups are also managed by the service.
If the automatic backup feature is enabled, new backups will be created according to your backup schedule, which can be set on the “instance overview” tab.
It is also possible to launch manual backups by clicking on the Create a backup button from the backups tab.
You can increase the storage capacity for your Database Instance by using the Scale up function from the management console. It allows you to migrate your database to a more powerful instance.
To import data into your Scaleway Elements Database, export your data using the
pg_dump command in a first step:
pg_dump -h OLD_DB_IP -p OLD_DB_PORT -U OLD_DB_USERNAME -F c -b -v -f "/usr/local/backup/database.backup" DATABASE_NAME
Once the data is exported, import the database using the
pg_restore -h INSTANCE_IP -p INSTANCE_PORT -U USERNAME -d DATABASE_NAME -v "/usr/local/backup/database.backup"
The different parameters used in the commands represent the following values:
--host): IP address of the host
--port): Port number of the host
--username): PostgreSQL user
cjust after a
-Fmeans that the format is the binary format specific to postgreSQL
--blobs): Specifies the binary string type
--file): Specifies the file name