Interacting with the registry database through pgAdmin

🌐 This document is available in both English and Ukrainian. Use the language toggle in the top right corner to switch between versions.

The pgAdmin tool enables you to view changes in the registry database and work with tables and other data structures.

To use the tool, perform the following steps:

  1. Sign in to the Control Plane admin console.

  2. Go to Registries > Quick links > Registry administrative zone.

  3. Click the Registry data viewing service (pgAdmin) link.

    db connection pgadmin 1

    Alternative method

    1. Sign in to the OpenShift console.

    2. Open the Projects section and select your registry.

    3. Go to Networking > Routes and search for pgadmin service route.

      review db changes before merge 17
    Where do I find the credentials for pgadmin?

    To find the username and password for pgadmin, go to Workloads > Secrets and locate the pgadmin-secret secret.

    review db changes before merge 18

  4. In the pgAdmin interface, go to the Servers section and enter the password for the application_role system user to connect to the registry database server.

    review db changes before merge 19

    Where do I find the password for connecting to the registry database server?

    To find the password for connecting to the Registry database server for the application_role user, go to Workloads > Secrets and locate the citus-roles-secrets secret. Copy the password from the appRolePass field.

    review db changes before merge 20

    review db changes before merge 21

  5. Find the registry operational database and review the changes. It is available via the following path:

    Servers > Registry > Databases > registry

    db connection pgadmin 2

    For details on viewing data in temporary databases, see registry-develop:best-practices/review-db-changes-before-merge.adoc.

    • To view the tables, use the following path: Schemas > registry > Tables.

      db connection pgadmin 3

    • To view the search conditions, use the following path: Schemas > registry > Views.

      db connection pgadmin 4

      In the database, search conditions are presented as view tables intended only for reading data. The naming convention for search conditions at the data model and database levels coincide with one exception: in the database, the _v suffix is added to the name of each search condition.

      For example, if you created a search condition called get_parent_by_name, the view table will have the following name: get_parent_by_name_v.