postgrespro.git / summary / log / commit / refs

commit    bb20f2c80d81377b036b1a673261ca842282ee10
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Tue May 05 20:06:49 2020 +0000

    Doc: warn that timezone abbreviations don't work in recovery_target_time.
    
    Moving this setting into the main configuration file was ill-considered,
    perhaps, because that typically causes it to be set before
    timezone_abbreviations has been set.  Which in turn means that zone
    abbreviations don't work, only full zone names.
    
    We could imagine hacking things so that such cases do work, but the
    stability of the hack would be questionable, and the value isn't really
    that high.  Instead just document that you should use a numeric zone
    offset or a full zone name.
    
    Per bug #16404 from Reijo Suhonen.
    Back-patch to v12 where this was changed.
    
    Discussion: https://postgr.es/m/16404-4603a99603fbd04c@postgresql.org


 doc/src/sgml/config.sgml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index a14df06292..48d1c8d641 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -3468,6 +3468,16 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"'  # Windows
         The precise stopping point is also influenced by
         <xref linkend="guc-recovery-target-inclusive"/>.
        </para>
+
+       <para>
+        The value of this parameter is a time stamp in the same format
+        accepted by the <type>timestamp with time zone</type> data type,
+        except that you cannot use a time zone abbreviation (unless the
+        <xref linkend="guc-timezone-abbreviations"/> variable has been set
+        earlier in the configuration file).  Preferred style is to use a
+        numeric offset from UTC, or you can write a full time zone name,
+        e.g. <literal>Europe/Helsinki</literal> not <literal>EEST</literal>.
+       </para>
       </listitem>
      </varlistentry>
 


[parent: 98c017c5760c]