mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-07 05:22:56 +00:00
Neon doesn't have seqscan detection of its own, so stop read_stream from trying to utilize that readahead, and instead make it issue readahead of its own. ## Problem @knizhnik noticed that we didn't issue smgrprefetch[v] calls for seqscans in PG17 due to the move to the read_stream API, which assumes that the underlying IO facilities do seqscan detection for readahead. That is a wrong assumption when Neon is involved, so let's remove the code that applies that assumption. ## Summary of changes Remove the cases where seqscans are detected and prefetch is disabled as a consequence, and instead don't do that detection. PG PR: https://github.com/neondatabase/postgres/pull/532
19 lines
305 B
JSON
19 lines
305 B
JSON
{
|
|
"v17": [
|
|
"17.2",
|
|
"01fa3c48664ca030cfb69bb4a350aa9df4691d88"
|
|
],
|
|
"v16": [
|
|
"16.6",
|
|
"81428621f7c04aed03671cf80a928e0a36d92505"
|
|
],
|
|
"v15": [
|
|
"15.10",
|
|
"8736b10c1d93d11b9c0489872dd529c4c0f5338f"
|
|
],
|
|
"v14": [
|
|
"14.15",
|
|
"13ff324150fceaac72920e01742addc053db9462"
|
|
]
|
|
}
|