Re: Problem while setting the fpw with SIGHUP

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Robert Haas <robertmhaas@gmail.com>

Cc: Amit Kapila <amit.kapila16@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, Dilip Kumar <dilipbalaut@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2018-04-23T23:52:17Z

Lists: pgsql-hackers

On Mon, Apr 23, 2018 at 12:21:04PM -0400, Robert Haas wrote:
> Fine, but that doesn't answer the question of whether we actually need
> to or should change the behavior in the first place.

Per the last arguments that would be "No, we don't want to change it as
it would surprise some users":
https://www.postgresql.org/message-id/20180420010402.GF2024@paquier.xyz
--
Michael

Commits

Fix assertion failure when updating full_page_writes for checkpointer.
- 85cc9c4e2da8 9.5.15 landed
- e315bd7db96a 9.6.11 landed
- 8256d7ae9ee3 10.6 landed
- 6c8671bc395c 11.0 landed
- a86bf6057edf 12.0 landed
Attach FPI to the first record after full_page_writes is turned on.
- 47a589c1fe35 9.5.15 landed
- fd4f2af774db 9.6.11 landed
- ede7d8192ca3 10.6 landed
- ff4220ead2c8 11.0 landed
- bc153c941d2e 12.0 landed
Revamp the WAL record format.
- 2c03216d8311 9.5.0 cited
Move the backup-block logic from XLogInsert to a new file, xloginsert.c.
- 2076db2aea76 9.5.0 cited