After a publisher flushes a batch of messages the batch is (obviously) not received immediately by the service. While the batch remains pending it potentially consumes memory resources in the client (and/or the service).
Some applications may have constraints on the number of bytes and/or messages they can tolerate in this pending state, and may prefer to block or reject messages.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["This page lists documentation for the `MaxPendingMessagesOption` within the Google Cloud Pub/Sub C++ client library, spanning versions from 2.11.0 to the latest release candidate 2.37.0-rc."],["The `MaxPendingMessagesOption` relates to the maximum number of messages a publisher can have pending after flushing a batch, but before they are fully processed by the service."],["This option is relevant for managing memory usage and controlling the flow of messages, allowing applications to avoid exceeding memory constraints or implement custom handling of pending messages."],["The `MaxPendingMessagesOption` is a type alias for `std::size_t`, indicating that it represents a size value."]]],[]]
