The following topics explain how to install and uninstall PSQL on Linux, macOS, and Raspbian.

Before installing or upgrading PSQL Server, Vx Server, or Client, review the following information:

You must be logged in as root to install any of the products. If you are installing from a CD, you must be at the CD root directory.

If you have any trouble with an installation, see Troubleshooting After Installation.

PSQL offers the following 64-bit full and client installations:

A full installation includes the engine and client files, utilities, and the complete user documentation. Client installations provide only files needed to support a client, including utilities and documentation. If you have 32-bit applications, support is provided as an additional client access installation. The following table lists the installation packages.

On Raspbian systems, PSQL provides a subset of the command line utilities that are available in full installations. These utilities consist of the following:

The Server Message Block (SMB) protocol enables network access to the PSQL MicroKernel Engine from a Linux, macOS, or Raspbian client at the Btrieve file level. You can find information about SMB-compatible file sharing at www.samba.org. For more information on remote Btrieve-level access, see Supported Path Formats for Samba.

If your database server engine fails to meet certain installation requirements, your applications may receive the status code “ 3031: Linux requester cannot connect to this server,” indicating a client-server incompatibility. In some cases, you may receive “ 94: The application encountered a permission error.”

The RPM format allows you to install PSQL if your Linux distribution contains the Red Hat Package Manager (RPM).

The following topics explain how to install PSQL products using RPM:

If you have any trouble with installation, see Troubleshooting After Installation.

Choose the package name to use for the installation using the following table and the distribution media.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

The package manager copies all necessary files onto disk (default location is /usr/local/psql) and runs a post-installation script which performs the following tasks:

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new release of the product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The name of the PSQL Client installation package follows these conventions:

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

If you need to provide 32-bit client access for an application, you must install the PSQL Client 64-bit first, and then add PSQL Client Access 32-bit. Otherwise, the steps are the same.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new release of the product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The tape archive (TAR) format allows you to install PSQL on Linux, macOS, and Raspbian. The following topics explain how to install PSQL products using TAR:

If you have any trouble with installation, see Troubleshooting After Installation.

The name of the PSQL Server installation package follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

The 64-bit installation scripts perform the following tasks:

The installation is complete. For additional information, see Installing PSQL Using TAR.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The name of the PSQL Server installation package follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

The 64-bit installation scripts perform the following tasks:

You must be logged in as a user with administrator rights to use the sudo command.

The installation is complete. For additional information, see After Installing PSQL on Linux, macOS, or Raspbian.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The name of the PSQL Client installation package follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

If you need to provide 32-bit client access for an application, you must install the PSQL Client 64-bit first, and then add PSQL Client Access 32-bit. The installation steps are the same except for the pre- and post-install scripts, as described below. Note that 32-bit client access does not apply to Raspbian systems.

The TAR installation is complete. For additional information, see After Installing PSQL on Linux, macOS, or Raspbian and Setting Up Network Communications for Clients.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The name of the PSQL Client installation package follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

You must be logged in as a user with administrator rights to use the sudo command.

The TAR installation is complete. For additional information, see After Installing PSQL on Linux, macOS, or Raspbian and Setting Up Network Communications for Clients.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

On macOS, you can install PSQL using a native Apple disk image (DMG). A DMG is a container file commonly used to distribute applications for macOS.

The following topics explain how to install PSQL products using DMG:

If you have any trouble with installation, see Troubleshooting After Installation.

The name of the PSQL Server DMG follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

The 64-bit installation scripts perform the following tasks:

The installation is complete. For possible next steps, see After Installing PSQL on Linux, macOS, or Raspbian.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The name of the PSQL Client DMG follows these conventions.

In the file name, yy.yy is a release number and zzz.zzz is a build number. See the file for its actual name.

Your installation is either a first time, with no previous version, or an upgrade to an existing installed version.

The installation is complete. For possible next steps, see After Installing PSQL on Linux, macOS, or Raspbian and Setting Up Network Communications for Clients.

If you have a previous version of PSQL already installed, you must uninstall that version and then install the new PSQL product. See Uninstalling PSQL on Linux, macOS, or Raspbian for more information.

The following topics may be useful after you install PSQL on Linux, macOS, or Raspbian:

The following table provides commands with which you can verify which packages the RPM packager installed. The commands are case sensitive.

Optionally, after the installation script finishes, you can verify that the database engine is running with the ps command. To do this, enter the following at a command prompt:

Generally, the default configuration settings for PSQL Server and Vx Server are sufficient. See Configuration for settings that you may want or need to set.

If you want to explore all of the configuration settings, see Configuration Reference in Advanced Operations Guide.

All configuration settings for the PSQL client are discussed in Linux, macOS, and Raspbian Client Configuration Properties in Advanced Operations Guide.

In this guide, see also Installing PSQL Clients for Windows and Setting Up Network Communications for Clients for additional information about clients.

This information applies only to Linux, macOS, or Raspbian clients that use a static IP address. Ignore this subsection if you use DHCP and have a DSN to resolve named addresses.

When you monitor clients using the PSQL Monitor utility, the client IP address that gets transmitted across the network originates from the hosts file. If the system name and IP have not been added to the hosts file, network communication uses the local host IP address, which is 127.0.0.1 or ::1 (a loopback address).

If you change the loopback address to the correct IP, or if you add the system name and IP to the hosts file on the client, the client name is displayed correctly in the Monitor utility.

Once you have completed installation, you may need to update your license to increase the user count for PSQL Server, or to increase the session count or data in use limits for PSQL Vx Server. See Increase User Count or Data in Use in PSQL User's Guide.

If you have problems with your installation, see Troubleshooting After Installation or get help online from the PSQL knowledge base at the Actian website. The following are common questions after installation of the products:

The following table lists the primary directories and files that result from installing the PSQL products on Linux, macOS, or Raspbian. $PVSW_ROOT refers to the root directory where the files are installed. By default it is set to /usr/local/psql. Unless otherwise noted, the primary directories and files are the same for 32- and 64-bit products.

For an upgrade installation, your existing PSQL files were updated to the latest versions.

The documentation installed with PSQL Server includes the following:

Man pages are provided for the command line utilities. To make these man pages available, add $PVSW_ROOT/man to the MANPATH environment variable.

Man pages are installed with PSQL Server, Vx Server, and with PSQL Client. Command line utilities are also covered in the PSQL user documentation.

The PSQL Documentation Library contains the complete set of user documentation, including the user documentation for the PSQL engine and software developer’s kit.

The documentation library is integrated into PSQL Control Center (PCC). In the PCC window, you can access the documentation library in the Welcome tab opened from the Help menu or by pressing F1 (Windows) or Shift F1 (Linux).

The release notes in readme_psql.htm contain general information about the release, sometimes including late-breaking advice not yet covered in the user documentation. These release notes are located in the /usr/local/psql/docs/ directory and are linked in the Welcome tab opened from the Help menu in PCC. The Actian website posts the latest version of the release notes.

See Starting PCC on Linux in PSQL User's Guide and Starting DDF Builder from a Command Line in DDF Builder User’s Guide.

The following topics explain how to remove PSQL from your system.

The following table lists the RPM commands to uninstall PSQL packages on Linux. You must log in as the root user using the su command before executing any of the commands.

This topic provides a table that lists the shell scripts used to remove various PSQL installations. The uninstalling of a TAR package is slightly different for Linux, macOS, and Raspbian, as shown in the following steps.

You must be logged in as a user with administrator rights to use the sudo command.