diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2016-04-12 11:13:52 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2016-04-12 11:14:00 -0400 |
| commit | bdf7db81921deb99fd9d489cbcc635906c89e215 (patch) | |
| tree | 49fb1aa274a68b9a48dbfd1108a98263fd944758 /src/tutorial/funcs_new.c | |
| parent | 813b456ea21d4cf57b124bf855ec019c7a8099a7 (diff) | |
| download | postgresql-bdf7db81921deb99fd9d489cbcc635906c89e215.tar.gz postgresql-bdf7db81921deb99fd9d489cbcc635906c89e215.zip | |
In generic WAL application and replay, ensure page "hole" is always zero.
The previous coding could allow the contents of the "hole" between pd_lower
and pd_upper to diverge during replay from what it had been when the update
was originally applied. This would pose a problem if checksums were in
use, and in any case would complicate forensic comparisons between master
and slave servers. So force the "hole" to contain zeroes, both at initial
application of a generically-logged action, and at replay.
Alexander Korotkov, adjusted slightly by me
Diffstat (limited to 'src/tutorial/funcs_new.c')
0 files changed, 0 insertions, 0 deletions