I manage some PostgreSQL clusters on Linux. We have a Primary & two Standby
servers & for Production, there is also a DR server. We use repmgr for our HA
solution & the Standbys are cloned from the Primary using the repmgr standby
clone command.
My manager asked for a report of all the user
Christoph,
Thank you for your explanation.
That puts my mind at ease.
Regards, Karin
From: Christoph Moench-Tegeder
Sent: Friday, September 16, 2022 3:43 PM
To: Hilbert, Karin
Cc: pgsql-general@lists.postgresql.org
Subject: Re: New message in PostgreSQL log
I'm working on an implementation of PostgreSQL 13.8 on a Linux RHEL8 sandbox
environment.
The server & PostgreSQL have all been configured.
I started PostgreSQL & got the following messages in the log file:
2022-09-16 02:00:16 EDT [1918984]: [3-1] db=,user= LOG: starting PostgreSQL
13.8 on
I manage PostgreSQL v12.8 database clusters.
Our database clusters are on Linux VMs, with OS:
Flavor: redhat_7
Release: 3.10.0-1160.45.1.el7.x86_64
We have repmgr clusters of 1 Primary & 2 Standby servers & use another server
with PgBouncer to direct the connections to the current Primary.
Thanks for the explanation, Tom.
From: Tom Lane
Sent: Thursday, October 28, 2021 11:04 AM
To: Hilbert, Karin
Cc: pgsql-general@lists.postgresql.org
Subject: Re: How to Resolve Data Being Truncated or Rounded Up During
PostgreSQL Migration from v9.623
I manage a PostgreSQL databases - we currently have clusters on PostgreSQL
v9.6.23 & PostgreSQL v12.8.
Our database clusters are on Linux VMs, with OS:
Flavor: redhat_7
Release: 3.10.0-1160.45.1.el7.x86_64
We have repmgr clusters of 1 Primary & 2 Standby servers & use another server
with
I manage a PostgreSQL database cluster - PostgreSQL v12.4.
Our database cluster is on a Linux VM, with OS:
Flavor: redhat_7
Release: 3.10.0-1160.15.2.el7.x86_64
We have a repmgr cluster of 1 Primary & 2 Standby servers & use another server
with PgBouncer to direct the connections to the
We have PostgreSQL v9.6 & also PostgreSQL v11.8 installed on various Linux VMs
with Red Hat Enterprise Linux Server release 7.8 (Maipo) OS. We're also
running repmgr v5.1.0 & PgBouncer v1.13.
We're getting vulnerability reports from our Security Office for the following
packages:
-
Hello,
We're in the process of building a new PostgreSQL environment on Scientific
Linux release 7.6.
The new environment will have a Primary & 2 Standby servers & have asynchronous
replication. It will use repmgr to manage failover/switchover events.
In the past, we've always had separate
After a database was updated by the application, a schema dump showed the
following default privilege statements:
--
-- Name: DEFAULT PRIVILEGES FOR SEQUENCES; Type: DEFAULT ACL; Schema: public;
Owner: gitlab_dbo
--
ALTER DEFAULT PRIVILEGES FOR ROLE IN SCHEMA public REVOKE ALL ON
SEQUENCES
hat standard for
PostgreSQL databases? Is there any reason to keep the names different between
the environments?
Thanks again for your help.
Regards,
Karin
From: Stephen Frost
Sent: Monday, January 21, 2019 1:53:00 PM
To: Hilbert, Karin
Cc: pgsql-general@li
Does anyone manage a PostgreSQL database for a GITLAB application?
I have PostgreSQL v9.6 installed on my server & we are trying to migrate a
GITLAB database there.
The developer says that we need to use the public schema instead of the schema
of the same name as the application user.
The
12 matches
Mail list logo
