From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Further cleanup of ReorderBufferCommit(). |
Date: | 2015-01-26 03:50:09 |
Message-ID: | E1YFagj-0002Gx-4A@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Further cleanup of ReorderBufferCommit().
On closer inspection, we can remove the "volatile" qualifier on
"using_subtxn" so long as we initialize that before the PG_TRY block,
which there's no particularly good reason not to do.
Also, push the "change" variable inside the PG_TRY so as to remove
all question of whether it needs "volatile", and remove useless
early initializations of "snapshow_now" and "using_subtxn".
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/c70f9e8988c52ee4a81b978208dda96d399977b6
Modified Files
--------------
src/backend/replication/logical/reorderbuffer.c | 34 +++++++++++------------
1 file changed, 17 insertions(+), 17 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-01-26 16:58:06 | pgsql: Fix volatile-safety issue in asyncQueueReadAllNotifications(). |
Previous Message | Tom Lane | 2015-01-26 01:19:14 | pgsql: Clean up assorted issues in ALTER SYSTEM coding. |