diff options
| -rw-r--r-- | src/backend/storage/lmgr/README.barrier | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/storage/lmgr/README.barrier b/src/backend/storage/lmgr/README.barrier index 4e37a4acbe7..e73d6799abc 100644 --- a/src/backend/storage/lmgr/README.barrier +++ b/src/backend/storage/lmgr/README.barrier @@ -38,7 +38,7 @@ Surprisingly, however, the second backend could also end up with foo = 0 and bar = 1. The compiler might swap the order of the two stores performed by the first backend, or the two loads performed by the second backend. Even if it doesn't, on a machine with weak memory ordering (such as PowerPC -or Itanium) the CPU might choose to execute either the loads or the stores +or ARM) the CPU might choose to execute either the loads or the stores out of order. This surprising result can lead to bugs. A common pattern where this actually does result in a bug is when adding items |