[HACKERS] pg_export_snapshot doc - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject [HACKERS] pg_export_snapshot doc
Date
Msg-id 20170407.192026.2237397371887622408.t-ishii@sraoss.co.jp
Whole thread Raw
List pgsql-hackers
pg_export_snapshot() cannot be used during recovery (i.e. on standby
servers), but it's not documented. IMO this is a bug and should be
fixed. Patch attached.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index cb0a36a..9923e67 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -18778,6 +18778,7 @@ postgres=# SELECT * FROM pg_walfile_name_offset(pg_stop_backup());    Snapshots are exported
withthe <function>pg_export_snapshot</> function,    shown in <xref
linkend="functions-snapshot-synchronization-table">,and    imported with the <xref linkend="sql-set-transaction">
command.
+    This function cannot be used during recovery.   </para>   <table id="functions-snapshot-synchronization-table">

pgsql-hackers by date:

Previous
From: Prakash Itnal
Date:
Subject: [HACKERS] Performance issue with postgres9.6
Next
From: Maksim Milyutin
Date:
Subject: Re: [HACKERS] Declarative partitioning - another take