pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Fetch XIDs atomically during vac_truncate_clog(). 6+ messages / 1 participants [nested] [flat]
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ REL9_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/ff98ae908bbfd950e98099c653380b9cd0ac2739 Modified Files -------------- src/backend/commands/vacuum.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ master Details ------- http://git.postgresql.org/pg/commitdiff/2d2e40e3befd8b9e0d2757554537345b15fa6ea2 Modified Files -------------- src/backend/commands/vacuum.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ REL9_4_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/edd8873ffede137e7af9cba5073ebb218e29704b Modified Files -------------- src/backend/commands/vacuum.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ REL9_5_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/bbbe2c97eba37fd8a9e580a596f48935f3d9ded8 Modified Files -------------- src/backend/commands/vacuum.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ REL9_1_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/5551dac59c0601b49d57a3f897fb0a6d581e58ac Modified Files -------------- src/backend/commands/vacuum.c | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Fetch XIDs atomically during vac_truncate_clog(). @ 2016-05-24 19:48 Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 6+ messages in thread From: Tom Lane @ 2016-05-24 19:48 UTC (permalink / raw) To: pgsql-committers Fetch XIDs atomically during vac_truncate_clog(). Because vac_update_datfrozenxid() updates datfrozenxid and datminmxid in-place, it's unsafe to assume that successive reads of those values will give consistent results. Fetch each one just once to ensure sane behavior in the minimum calculation. Noted while reviewing Alexander Korotkov's patch in the same area. Discussion: <8564.1464116473@sss.pgh.pa.us> Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/4cf0978ea2733548149ee7f11e588975daaf7609 Modified Files -------------- src/backend/commands/vacuum.c | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2016-05-24 19:48 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us> 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us> 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us> 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us> 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us> 2016-05-24 19:48 pgsql: Fetch XIDs atomically during vac_truncate_clog(). Tom Lane <tgl@sss.pgh.pa.us>
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