From 0ca084d676f701608228f5c34e7cc9bc06e37374 Mon Sep 17 00:00:00 2001
From: Steven Fackler <sfackler@gmail.com>
Date: Thu, 17 Jan 2019 20:45:51 -0800
Subject: [PATCH] Add ordering note

---
 tokio-postgres/src/lib.rs | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tokio-postgres/src/lib.rs b/tokio-postgres/src/lib.rs
index 9a18af49..5c8779e9 100644
--- a/tokio-postgres/src/lib.rs
+++ b/tokio-postgres/src/lib.rs
@@ -49,6 +49,12 @@
 //! tokio::run(fut);
 //! ```
 //!
+//! # Behavior
+//!
+//! Calling a method like `Client::query` on its own does nothing. The associated request is not sent to the database
+//! until the future returned by the method is first polled. Requests are executed in the order that they are first
+//! polled, not in the order that their futures are created.
+//!
 //! # Pipelining
 //!
 //! The client supports *pipelined* requests. Pipelining can improve performance in use cases in which multiple,