Unable to find the details of bug fix in 9.6.x minor version.

From: Sameer Malve <malvesameer(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Unable to find the details of bug fix in 9.6.x minor version.
Date: 2020-06-03 09:32:26
Message-ID: CAEGp0dhsXpXWgkvXeCx=s=qu8bJeMd1keXvgZ-Bt-tzf4gHA7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Team,

I am seeing in postgresql release notes that below bugs are fix in 9.6.x
version but unable to find the details for about that bug .

*Fixed in 9.6.11*

Fix unexpected timeouts when using wal_sender_timeout on a slow server
(Noah Misch) .

*Fixed in 9.6.12*

1. A new server parameter data_sync_retry has been added to control this;
if you are certain that your kernel does not discard dirty data buffers in
such scenarios, you can set data_sync_retry to on to restore the old
behavior.
2. Fix logic for stopping a subset of WAL senders when synchronous
replication is enabled
3. Make the archiver prioritize WAL history files over WAL data files while
choosing which file to archive next

*Fixed in 9.6.16*

Ensure that temporary WAL and history files are removed at the end of
archive recovery.

Avoid unwanted delay during shutdown of a logical replication walsender.

*Fixed in 9.6.17*

Fix failure in logical replication publisher after a database crash and
restart

*Fixed in 9.6.18:*

This can eliminate many attempts to fetch non-existent WAL files from
archive storage, which is helpful if archive access is slow.

Regards,
Sameer Malve

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Azul 2020-06-03 11:04:07 select count(id) on RDS replica causing high CPU load on RDS master
Previous Message Kyotaro Horiguchi 2020-06-03 09:00:36 Re: canceling statement due to conflict with recovery after pg_basebackup