From 0ff56a59d2496a8f896362b91d1faa9b14f6a6d9 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 27 Oct 2017 10:46:06 -0400
Subject: [PATCH] Doc: mention that you can't PREPARE TRANSACTION after NOTIFY.

The NOTIFY page said this already, but the PREPARE TRANSACTION page
missed it.

Discussion: https://postgr.es/m/20171024010602.1488.80066@wrigleys.postgresql.org
---
 doc/src/sgml/ref/prepare_transaction.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/prepare_transaction.sgml b/doc/src/sgml/ref/prepare_transaction.sgml
index 626753f5762..50a93b45dd3 100644
--- a/doc/src/sgml/ref/prepare_transaction.sgml
+++ b/doc/src/sgml/ref/prepare_transaction.sgml
@@ -100,7 +100,8 @@ PREPARE TRANSACTION <replaceable class="PARAMETER">transaction_id</replaceable>
    It is not currently allowed to <command>PREPARE</> a transaction that
    has executed any operations involving temporary tables,
    created any cursors <literal>WITH HOLD</>, or executed
-   <command>LISTEN</> or <command>UNLISTEN</>.
+   <command>LISTEN</>, <command>UNLISTEN</>, or
+   <command>NOTIFY</>.
    Those features are too tightly
    tied to the current session to be useful in a transaction to be prepared.
   </para>