database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

C comment: fix wording about shared memory message queue

Browse Source 
Reported-by: Tels

Discussion: https://postgr.es/m/e66e05bc55f5ce904e361ad17a3395ae.squirrel@sm.webmail.pair.com
This commit is contained in:
Bruce Momjian 2018-03-29 12:18:34 -04:00
parent 851a26e266
commit bc0021ef09
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/backend/storage/ipc/shm_mq.c
View File

@ -493,7 +493,7 @@ shm_mq_sendv(shm_mq_handle *mqh, shm_mq_iovec *iov, int iovcnt, bool nowait)
return SHM_MQ_DETACHED; return SHM_MQ_DETACHED;
/* /*
* If the counterpary is known to have attached, we can read mq_receiver * If the counterparty is known to have attached, we can read mq_receiver
* without acquiring the spinlock and assume it isn't NULL. Otherwise, * without acquiring the spinlock and assume it isn't NULL. Otherwise,
* more caution is needed. * more caution is needed.
*/ */
@ -1203,9 +1203,9 @@ shm_mq_inc_bytes_read(shm_mq *mq, Size n)
/* /*
* Separate prior reads of mq_ring from the increment of mq_bytes_read * Separate prior reads of mq_ring from the increment of mq_bytes_read
* which follows. Pairs with the full barrier in shm_mq_send_bytes(). We * which follows. This pairs with the full barrier in shm_mq_send_bytes().
* only need a read barrier here because the increment of mq_bytes_read is * We only need a read barrier here because the increment of mq_bytes_read
* actually a read followed by a dependent write. * is actually a read followed by a dependent write.
*/ */
pg_read_barrier(); pg_read_barrier();