summaryrefslogtreecommitdiff
path: root/src/include/replication
diff options
context:
space:
mode:
authorTom Lane2017-06-21 18:09:24 +0000
committerTom Lane2017-06-21 18:09:24 +0000
commit9ef2dbefc7fb3ac22e1528bc22a41a5c6c6a9539 (patch)
treeb8d70c272e84239c11a71727ccdf1dd147e40a5e /src/include/replication
parentbcbf392ec84362040faf72daad22c647c74e2b2a (diff)
Final pgindent run with old pg_bsd_indent (version 1.3).
This is just to have a clean basis for comparison with the results of the new version (which will indeed end up reverting some of these changes...) Discussion: https://postgr.es/m/E1dAmxK-0006EE-1r@gemulon.postgresql.org Discussion: https://postgr.es/m/30527.1495162840@sss.pgh.pa.us
Diffstat (limited to 'src/include/replication')
-rw-r--r--src/include/replication/reorderbuffer.h6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/include/replication/reorderbuffer.h b/src/include/replication/reorderbuffer.h
index 8d8d418e8e3..1d9a1d343e7 100644
--- a/src/include/replication/reorderbuffer.h
+++ b/src/include/replication/reorderbuffer.h
@@ -214,9 +214,9 @@ typedef struct ReorderBufferTXN
/*
* Has this transaction been spilled to disk? It's not always possible to
- * deduce that fact by comparing nentries with nentries_mem, because
- * e.g. subtransactions of a large transaction might get serialized
- * together with the parent - if they're restored to memory they'd have
+ * deduce that fact by comparing nentries with nentries_mem, because e.g.
+ * subtransactions of a large transaction might get serialized together
+ * with the parent - if they're restored to memory they'd have
* nentries_mem == nentries.
*/
bool serialized;