public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: [email protected] <[email protected]>
Subject: Re: Failing streaming replication on PostgreSQL 14
Date: Mon, 15 Apr 2024 08:36:42 -0400
Message-ID: <CANzqJaCYMiFCdy2hd7ZVhhspB6Y4CiWPFyVdLY36vxSX+NSfCQ@mail.gmail.com> (raw)
In-Reply-To: <2UjR_dq61Dzm98Vci6oYDLK4PlmvAzhbVg0uYCunualePnYCN8sYSXVuJW2N4D1kHqiWPw7VvEZMYS0Hy4UHfRI6lVApRrs_1-LZ3E0jzNE=@seinlet.com>
References: <2UjR_dq61Dzm98Vci6oYDLK4PlmvAzhbVg0uYCunualePnYCN8sYSXVuJW2N4D1kHqiWPw7VvEZMYS0Hy4UHfRI6lVApRrs_1-LZ3E0jzNE=@seinlet.com>

On Mon, Apr 15, 2024 at 2:53 AM Nicolas Seinlet <[email protected]> wrote:

> Hello everyone,
>
> Since I moved some clusters from PostgreSQL 12 to 14, I noticed random
> failures in streaming replication. I say "random" mostly because I haven't
> got the source of the issue.
>
> I'm using the Ubuntu/cyphered ZFS/PostgreSQL combination. I'm using Ubuntu
> LTS (20.04 22.04) and provided ZFS/PostgreSQL with LTS (PostgreSQL 12 on
> Ubuntu 20.04 and 14 on 22.04).
>
> The streaming replication of PostgreSQL is configured with
> `primary_conninfo 'host=main_server port=5432 user=replicant
> password=a_very_secure_password sslmode=require
> application_name=replication_postgresql_app' ` , no replication slot nor
> restore command, and the wal is configured with `full_page_writes = off
> wal_init_zero = off wal_recycle = off`
>
> If this works like a charm on PostgreSQL 12, it's sometimes failing with
> PostgreSQL 14. As we also changed the OS, maybe the issue relies somewhere
> else.
>
> When the issue is detected, the WAL on the primary is correct. A piece of
> the WAL is wrong on the secondary. Only some bytes. Some bytes later, the
> wal is again correct. Stopping PostgreSQL on the secondary, removing the
> wrong WAL file, and restarting PostgreSQL solves the issue.
>
> We've added another secondary and noticed the issue can appear on one of
> the secondaries, not both at the same time.
>
> What can I do to detect the origin of this issue?
>

1. Minor version number?
2. Using replication_slots?
3. Error message(s)?

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Failing streaming replication on PostgreSQL 14
  In-Reply-To: <CANzqJaCYMiFCdy2hd7ZVhhspB6Y4CiWPFyVdLY36vxSX+NSfCQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox