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"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-04-17 UTC."],[[["The content provides a list of different versions of a C++ library related to Google Cloud Pub/Sub, ranging from version 2.11.0 up to the latest release candidate, 2.37.0-rc."],["Each version listed corresponds to a specific documentation page for the `MaxPendingMessagesOption` structure within the library."],["`MaxPendingMessagesOption` manages the maximum number of messages that can be pending (not yet acknowledged) after a publisher has flushed a batch, which helps control memory consumption."],["The type alias for the `MaxPendingMessagesOption` is `std::size_t`, indicating it represents a size or count."],["The content shows how different versions manage pending messages in the client, which might block or reject them based on the number or size."]]],[]]
