Am 25.06.2025 um 01:20 schrieb Greg Sabino Mullane:
On Mon, Jun 23, 2025 at 2:45 PM raphi wrote:
As of now though we cannot use PG for any PCI/DSS certified
application
because we can't enforce either complexity nor regular password
changes,
You can, and many, many companie
On 6/24/25 08:38, Kouber Saparev wrote:
Barman is involved indeed, its version is 3.14. The command: "barman
backup xxx --incremental latest".
I don't use Barman and I am still figuring out incremental backups, so
what I say should be taken lightly.
From here:
https://docs.pgbarman.org/rele
On Mon, Jun 23, 2025 at 2:45 PM raphi wrote:
> As of now though we cannot use PG for any PCI/DSS certified application
> because we can't enforce either complexity nor regular password changes,
>
You can, and many, many companies do, but you need a modern auth system
like Kerberos. Even if we we
Barman is involved indeed, its version is 3.14. The command: "barman backup
xxx --incremental latest".
PostgreSQL is version 17.3.
На вт, 24.06.2025 г. в 18:26 Adrian Klaver
написа:
> On 6/24/25 02:31, Kouber Saparev wrote:
> > Hello,
> >
> > We are trying to use pg_combinebackup but eventually
On 6/24/25 02:31, Kouber Saparev wrote:
Hello,
We are trying to use pg_combinebackup but eventually it fails with:
What is the command you are using to take the incremental backups?
What version of Postgres are you taking the incremental backups from?
Given the naming below, is Barman involv
Le 24/06/2025 à 07:18, raphi a écrit :
Am 23.06.2025 um 22:39 schrieb Christoph Berg:
Re: raphi
Sorry for this rather long (first) email on this list but I feel
like I had
to explain our usecase and why LDAP is not always as simple as
adding a line
to hba.conf.
Did you give the "pam" metho
Hello,
We are trying to use pg_combinebackup but eventually it fails with:
pg_combinebackup --debug --dry-run
--output=/barman-backup/barman-data/test_combine 20250616T140003/data
20250617T090005/data
...
pg_combinebackup: would copy "20250616T140003/data/base/16420/2136674204"
to "/barman-back
On 23.06.2025 16:33, Dmitry wrote:
Hi,
The problem is as follows.
A replication cluster includes a primary server and one hot-standby replica.
The workload on the primary server is represented by multiple requests
generating multixact IDs, while the hot-standby replica performs reading
request
