/*
* Optimization for other than "Command Complete", "Ready For query",
- * "Error response" and "Notice message" messages. Especially, since it
- * is too often to receive and forward "Data Row" message, we do not flush
- * the message to frontend now. We expect that "Command Complete" message
- * (or "Error response" or "Notice response" message) follows the stream
- * of data row message anyway, so flushing will be done at that time.
+ * "Error response" ,"Notice message" and "Notification response"
+ * messages. Especially, since it is too often to receive and forward
+ * "Data Row" message, we do not flush the message to frontend now. We
+ * expect that "Command Complete" message (or "Error response" or "Notice
+ * response" message) follows the stream of data row message anyway, so
+ * flushing will be done at that time.
*
* Same thing can be said to CopyData message. Tremendous number of
* CopyData messages are sent to frontend (typical use case is pg_dump).
* So eliminating per CopyData flush significantly enhances performance.
*/
- if (kind == 'C' || kind == 'Z' || kind == 'E' || kind == 'N')
+ if (kind == 'C' || kind == 'Z' || kind == 'E' || kind == 'N' || kind == 'A')
{
pool_write_and_flush(frontend, p1, len1);
}