pgsql: Revert "Use group updates when setting transaction status in clo

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Revert "Use group updates when setting transaction status in clo
Date: 2017-03-10 19:53:32
Message-ID: E1cmQbU-0003MH-Cz@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Revert "Use group updates when setting transaction status in clog."

This reverts commit ccce90b398673d55b0387b3de66639b1b30d451b. This
optimization is unsafe, at least, of rollbacks and rollbacks to
savepoints, but I'm concerned there may be other problematic cases as
well. Therefore, I've decided to revert this pending further
investigation.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/390811750d1647ed81a462da3af7f1fd66166e95

Modified Files
--------------
src/backend/access/transam/clog.c | 239 ++--------------------------------
src/backend/access/transam/twophase.c | 2 +-
src/backend/storage/lmgr/proc.c | 9 --
src/include/access/twophase.h | 13 --
src/include/storage/proc.h | 14 --
5 files changed, 9 insertions(+), 268 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-03-10 20:18:44 pgsql: Reduce log verbosity of startup/shutdown for launcher subprocess
Previous Message Andres Freund 2017-03-10 19:47:58 Re: pgsql: contrib/amcheck needs RecentGlobalXmin to be PGDLLIMPORT'ified.