Flush all remaining rows inside connection buffer if

[github-actions]

any are remaining.

The Flush message does not cause any specific
output to be generated, but forces the backend to deliver any data
pending in its output buffers. A Flush must be sent after any
extended-query command except Sync, if the frontend wishes to examine
the results of that command before issuing more commands. Without
Flush, messages returned by the backend will be combined into the
minimum possible number of packets to minimize network overhead.
https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY

Line: 166

psql-wire//command.go

Lines 163 to 173 in 3dbc832

	case types.ClientBind:
	return srv.handleBind(ctx, reader, writer)
	case types.ClientFlush:
	// TODO: Flush all remaining rows inside connection buffer if
	// any are remaining.
	//
	// The Flush message does not cause any specific
	// output to be generated, but forces the backend to deliver any data
	// pending in its output buffers. A Flush must be sent after any
	// extended-query command except Sync, if the frontend wishes to examine
	// the results of that command before issuing more commands. Without