MONGOC_WRITE_CONCERN_GET_FSYNC(3)

πŸ’– MONGOC_WRITE_CONCERN_GET_FSYNC πŸ’–

okay bestie, so this one lives in libmongoc (that's the MongoDB C driver, iykyk) and it's the lil function that checks whether fsync is turned on in your write concern. yes it's a whole vibe, but heads up, it's giving legacy β€” more on that in a sec 🫢


⚠️ WARNING ⚠️

Deprecated since version 1.4.0 β€” use mongoc_write_concern_get_journal() instead. not me showing up to tell you your fave is old πŸ’€ like, this function still works, it's just not the moment anymore. go use the journal one, fr fr.

✨ SYNOPSIS ✨

bool
mongoc_write_concern_get_fsync (const mongoc_write_concern_t *write_concern);

like yes, it returns a bool, yes it takes one pointer, slay πŸ’…


πŸŽ€ PARAMETERS πŸŽ€

  • write_concern β€” a mongoc_write_concern_t. that's the whole thing bestie, one (1) argument, she's low maintenance πŸ’–

🌸 DESCRIPTION 🌸

so basically? it fetches whether an fsync should be performed before returning success on a write operation. that's it, that's the job β€” it goes and asks "hey, is fsync set in here?" and tells you. main character energy for a getter honestly πŸ‘‘


πŸ¦‹ RETURNS πŸ¦‹

returns true if fsync is set as part of the write concern. and if it's not set? then it's not true, bestie, do the math πŸ™ˆ


πŸ’œ AUTHOR πŸ’œ

MongoDB, Inc β€” the icons themselves, no cap 🌈


2009-present, MongoDB, Inc. all theirs, we're just vibing in it πŸ’«


and that's the whole page, periodt πŸŽ€ this was libmongoc 1.30.13, dated Oct 09, 2026 β€” love that for us, now go call mongoc_write_concern_get_journal() instead, mwah πŸ’…πŸ’–

πŸ“¦ where this page comes from