Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

miscadmin.h

Blame
    • Tom Lane's avatar
      45f64f1b
      Remove CTimeZone/HasCTZSet, root and branch. · 45f64f1b
      Tom Lane authored
      These variables no longer have any useful purpose, since there's no reason
      to special-case brute force timezones now that we have a valid
      session_timezone setting for them.  Remove the variables, and remove the
      SET/SHOW TIME ZONE code that deals with them.
      
      The user-visible impact of this is that SHOW TIME ZONE will now show a
      POSIX-style zone specification, in the form "<+-offset>-+offset", rather
      than an interval value when a brute-force zone has been set.  While perhaps
      less intuitive, this is a better definition than before because it's
      actually possible to give that string back to SET TIME ZONE and get the
      same behavior, unlike what used to happen.
      
      We did not previously mention the angle-bracket syntax when describing
      POSIX timezone specifications; add some documentation so that people
      can figure out what these strings do.  (There's still quite a lot of
      undocumented functionality there, but anybody who really cares can
      go read the POSIX spec to find out about it.  In practice most people
      seem to prefer Olsen-style city names anyway.)
      45f64f1b
      History
      Remove CTimeZone/HasCTZSet, root and branch.
      Tom Lane authored
      These variables no longer have any useful purpose, since there's no reason
      to special-case brute force timezones now that we have a valid
      session_timezone setting for them.  Remove the variables, and remove the
      SET/SHOW TIME ZONE code that deals with them.
      
      The user-visible impact of this is that SHOW TIME ZONE will now show a
      POSIX-style zone specification, in the form "<+-offset>-+offset", rather
      than an interval value when a brute-force zone has been set.  While perhaps
      less intuitive, this is a better definition than before because it's
      actually possible to give that string back to SET TIME ZONE and get the
      same behavior, unlike what used to happen.
      
      We did not previously mention the angle-bracket syntax when describing
      POSIX timezone specifications; add some documentation so that people
      can figure out what these strings do.  (There's still quite a lot of
      undocumented functionality there, but anybody who really cares can
      go read the POSIX spec to find out about it.  In practice most people
      seem to prefer Olsen-style city names anyway.)