mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-07 05:22:56 +00:00
b00a0096bf
## Problem See https://github.com/neondatabase/neon/issues/12387 `allocNewBuffer` initialise page with zeros but not always return it because of parity checks. In case of wrong parity the page is rejected and as a result we have dirty page with zero LSN, which cause assertion failure on neon_write when page is evicted from shared buffers. ## Summary of changes Perform, page initialisation in `allocNewBuffer` only when buffer is returned (parity check is passed). Postgres PRs: https://github.com/neondatabase/postgres/pull/661 https://github.com/neondatabase/postgres/pull/662 https://github.com/neondatabase/postgres/pull/663 https://github.com/neondatabase/postgres/pull/664 --------- Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech> Co-authored-by: Kosntantin Knizhnik <konstantin.knizhnik@databricks.com>
19 lines
305 B
JSON
19 lines
305 B
JSON
{
|
|
"v17": [
|
|
"17.5",
|
|
"fa1788475e3146cc9c7c6a1b74f48fd296898fcd"
|
|
],
|
|
"v16": [
|
|
"16.9",
|
|
"9b9cb4b3e33347aea8f61e606bb6569979516de5"
|
|
],
|
|
"v15": [
|
|
"15.13",
|
|
"aaaeff2550d5deba58847f112af9b98fa3a58b00"
|
|
],
|
|
"v14": [
|
|
"14.18",
|
|
"c9f9fdd0113b52c0bd535afdb09d3a543aeee25f"
|
|
]
|
|
}
|