mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-25 15:19:58 +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>
15 lines
375 B
Plaintext
15 lines
375 B
Plaintext
# ----------
|
|
# Like in PostgreSQL src/test/regress/parallel_schedule, we put no
|
|
# more than twenty tests in any one parallel group; this limits the
|
|
# number of connections needed to run the tests.
|
|
# ----------
|
|
|
|
test: neon-cid
|
|
test: neon-rel-truncate
|
|
test: neon-clog
|
|
test: neon-test-utils
|
|
test: neon-vacuum-full
|
|
test: neon-subxacts
|
|
test: neon-spgist
|
|
test: neon-event-triggers
|