Shared-NR PostgreSQL

About Shared NR - PostgreSQL Database

The Shared-NR uses PostgreSQL to provide as a Postgres service-relational database management system to store data securely for retrieval at the request of other software applications.

The PostgreSQL Database relational database management system (RDBMS) as a service on Predix, offers features that emphasize extensibility and standards compliance. PostgreSQL supports multiple data types such as, XML, JSON, arrays, geometric and many others in different domains.

The database can handle workloads ranging from single-machine apps to internet-facing applications with many concurrent users.

For more information and details about using PostgreSQL Database, see the PostgreSQL documentation.
Note: The Shared-NR plan is deprecated, no longer available, and will be decommissioned soon. If you are a current Shared-NR customer, you may continue using the service. (See status here). Please move to Postures 2.0 as soon as possible. Consider the following limitations as you continue to use your current Shared-NR plan:
  • New instances cannot be created
  • Current instances cannot be modified or enlarged.

PostgreSQL Features

High Availability and Scalability
The PostgreSQL Database architecture ensures high availability and automatic scaling. Postgres supports the Predix goal of 99.9 percent up time and automatically scales to add nodes as usage levels increase.

Each subscription plan has an associated storage restriction, concurrent connection limit, and other specific features such as data-at-rest encryption.

Daily Backups

All Postgres databases are backed up daily and uploaded to archive storage for 14 days as long as a service is active. All archived backups older than 14 days are automatically deleted.

Note: Custom business rules for individual databases cannot be defined for backups.
On-Demand Backup
An embedded Cloud Foundry application enables users to schedule a backup as needed for events such as, preparing for data migration, rolling out a system upgrade, or performing a bulk data upload. One on-demand backup is allowed per database, per day.
Replication and Failover
All subscription plans (with the exception of the shared-nr plan) replicate the database to a standby instance. If a failover is activated, all connections are automatically redirected to the standby instance. An outage of up to 30 minutes, Recovery Time Objective, (RTO) might occur until the transfer to the standby is complete and the standby is established as the new active database. The length of the outage during the failover depends on the number of write transactions that were in process at the time of the failure. In the rare case that the master database is completely down and the standby is unable to replicate the latest data, there will be a data loss; the new master will start without the latest replicated data within the RTO time.
Point-In-Time Recovery
Point-In-Time Recovery (PITR) backs up the system continuously so that data can be restored or recovered to a particular time in the past within the 7-day archival period.

Connecting to your Shared-NR PostgreSQL Database

Learn how to connect to your database and schedule backups.

Connecting to the PostgreSQL Database

About This Task

Use one of these ways to connect to the PostgreSQL Database:
Connect using PHPpgAdmin
  1. Follow the steps listed in this article: KB0010829
  2. Refer to the Admin description for database management options: https://github.com/cloudfoundry-community/phppgadmin-cf
Connect using PGStudio
  1. Download the Cloud Foundry version of PGStudio and push the application to your org/space.
  2. Refer to this PG Studio link for usage instructions: https://github.com/cloudfoundry-community/phppgadmin-cfhttps://github.com/john-k-ge/pg_studio_1.2_cf
Connect using a Predix HTTP Data Tunnel

https://digitalexchange.ge.com/solution/predix-http-data-tunnel

Deleting a Shared-NR PostgreSQL Database Service Instance

About This Task

You can remove the Shared NR PostgreSQL Database application and service instance.

Procedure

  1. Log into your Cloud Foundry account.
    cf login
  2. Stop the application by entering the following command:
    cf stop <application_name>
  3. Unbind your SQL Database service instance from the application.
    cf us <application_name> <my-postgres_service_instance>
  4. Remove the SQL Database application.
    cf d <application_name>
  5. Remove the SQL Database service instance.
    cf ds <my-postres_service_instance>
    The database is deleted.