How to Install and Uninstall postgresql10-pgaudit Package on openSuSE Tumbleweed
Last updated: November 07,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "postgresql10-pgaudit" package
In this section, we are going to explain the necessary steps to install postgresql10-pgaudit on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
postgresql10-pgaudit
Copied
2. Uninstall "postgresql10-pgaudit" package
This guide let you learn how to uninstall postgresql10-pgaudit on openSuSE Tumbleweed:
$
sudo zypper remove
postgresql10-pgaudit
Copied
3. Information about the postgresql10-pgaudit package on openSuSE Tumbleweed
Information for package postgresql10-pgaudit:
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : postgresql10-pgaudit
Version : 1.2.2-2.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 64,0 KiB
Installed : No
Status : not installed
Source package : postgresql10-pgaudit-1.2.2-2.2.src
Summary : An auditing module for PostgreSQL
Description :
This is the initial version of an auditing module for Postgres.
It collects audit events from various sources and logs them in CSV format
including a timestamp, user information, details of objects affected (if any),
and the fully-qualified command text (whenever available).
All DDL, DML (including SELECT), and utility commands are supported. These
are categorised as described below, and audit logging for each group of
commands may be enabled or disabled by the superuser. Once enabled, however,
audit logging may not be disabled by a user.
---------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : postgresql10-pgaudit
Version : 1.2.2-2.2
Arch : x86_64
Vendor : openSUSE
Installed Size : 64,0 KiB
Installed : No
Status : not installed
Source package : postgresql10-pgaudit-1.2.2-2.2.src
Summary : An auditing module for PostgreSQL
Description :
This is the initial version of an auditing module for Postgres.
It collects audit events from various sources and logs them in CSV format
including a timestamp, user information, details of objects affected (if any),
and the fully-qualified command text (whenever available).
All DDL, DML (including SELECT), and utility commands are supported. These
are categorised as described below, and audit logging for each group of
commands may be enabled or disabled by the superuser. Once enabled, however,
audit logging may not be disabled by a user.