pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Reset lastOverflowedXid on standby when needed 7+ messages / 1 participants [nested] [flat]
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL9_6_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7381b79ade479de5038ad924fbff1c584a0d6fee Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/774d00573966e40104337fd14153973a79abc5ce Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL_11_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/691c0df73a74786b1704b806132006a5754dff32 Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/8f779a1a3eb6716faf47ef10e7bf0b883b8a1170 Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/e1fee28a0441652f021045646808a772314798f9 Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b0f6bd48f35ddfe4195804eb8197f477c88da6d2 Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Reset lastOverflowedXid on standby when needed @ 2021-11-06 16:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 7+ messages in thread From: Alexander Korotkov @ 2021-11-06 16:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Reset lastOverflowedXid on standby when needed Currently, lastOverflowedXid is never reset. It's just adjusted on new transactions known to be overflowed. But if there are no overflowed transactions for a long time, snapshots could be mistakenly marked as suboverflowed due to wraparound. This commit fixes this issue by resetting lastOverflowedXid when needed altogether with KnownAssignedXids. Backpatch to all supported versions. Reported-by: Stan Hu Discussion: https://postgr.es/m/CAMBWrQ%3DFp5UAsU_nATY7EMY7NHczG4-DTDU%3DmCvBQZAQ6wa2xQ%40mail.gmail.com Author: Kyotaro Horiguchi, Alexander Korotkov Reviewed-by: Stan Hu, Simon Riggs, Nikolay Samokhvalov, Andrey Borodin, Dmitry Dolgov Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/05e6e78c1840d07154a4b52092178a2d1ad39445 Modified Files -------------- src/backend/storage/ipc/procarray.c | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2021-11-06 16:14 UTC | newest] Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2021-11-06 16:13 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:13 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:13 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:13 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:13 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:14 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org> 2021-11-06 16:14 pgsql: Reset lastOverflowedXid on standby when needed Alexander Korotkov <akorotkov@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox