</para>
<para>
- It is possible for NoticeResponse messages to be interspersed between
- CopyData messages; frontends must handle this case, and should be
- prepared for other asynchronous message types as well (see <xref
- linkend="protocol-async">). Otherwise, any message type other than
+ It is possible for NoticeResponse and ParameterStatus messages to be
+ interspersed between CopyData messages; frontends must handle these cases,
+ and should be prepared for other asynchronous message types as well (see
+ <xref linkend="protocol-async">). Otherwise, any message type other than
CopyData or CopyDone may be treated as terminating copy-out mode.
</para>
/*
* If it's a legitimate async message type, process it. (NOTIFY
* messages are not currently possible here, but we handle them for
- * completeness. NOTICE is definitely possible, and ParameterStatus
- * could probably be made to happen.) Otherwise, if it's anything
- * except Copy Data, report end-of-copy.
+ * completeness.) Otherwise, if it's anything except Copy Data,
+ * report end-of-copy.
*/
switch (id)
{