From f14ae5f905282109c9a2571c2048c564004f24c5 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Tue, 8 Mar 2011 23:59:52 -0500 Subject: [PATCH] Update alpha release notes for latest commits. --- doc/src/sgml/release-9.1.sgml | 49 +++++++++++++++++++++++------------ 1 file changed, 32 insertions(+), 17 deletions(-) diff --git a/doc/src/sgml/release-9.1.sgml b/doc/src/sgml/release-9.1.sgml index 2ea0fd7e21a..d14a2dce560 100644 --- a/doc/src/sgml/release-9.1.sgml +++ b/doc/src/sgml/release-9.1.sgml @@ -1,6 +1,6 @@ - + Release 9.1alpha4 @@ -122,6 +122,24 @@ + + + Synchronous replication + + + When enabled, transaction commit will wait for WAL records to be + replicated before informing the client that a transaction has + successfully committed. + + + + + + When recovery_target_timelines='latest', periodically + rescan the archive for new timelines + + + @@ -1011,15 +1029,14 @@ - Skip dropped attributes when converting Python objects to - tuples + Make plpy.Fatal() raise FATAL, rather than ERROR - Improve messages for errors in compiling anonymous - PL/Python blocks + Skip dropped attributes when converting Python objects to + tuples @@ -1043,11 +1060,17 @@ - Do not prefix error messages with the string - "PL/Python: " + Improve error reporting - - It is redundant, given the error context. + Better error messages for errors in compiling anonymous + PL/Python blocks. Avoid prefixing error messages with the string + "PL/Python: ", which is redundant, given the error + context. Provide a separate exception class for each error code + the backend defines, and make it possible to get the SQLSTATE from + the exception object. Report Python errors from iterators + using PLy_elog, so that the Python exception is included in the + exception, and to avoid setting the errcode to + ERRCODE_DATA_EXCEPTION. @@ -1095,14 +1118,6 @@ - - - Provide a separate exception class for each error code - the backend defines, and make it possible to get the SQLSTATE from - the exception object - - - Assorted code cleanup