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

strftime.c

Blame
    • Bruce Momjian's avatar
      aa8bdab2
      Attached patch gets rid of the global timezone in the following steps: · aa8bdab2
      Bruce Momjian authored
      * Changes the APIs to the timezone functions to take a pg_tz pointer as
      an argument, representing the timezone to use for the selected
      operation.
      
      * Adds a global_timezone variable that represents the current timezone
      in the backend as set by SET TIMEZONE (or guc, or env, etc).
      
      * Implements a hash-table cache of loaded tables, so we don't have to
      read and parse the TZ file everytime we change a timezone. While not
      necesasry now (we don't change timezones very often), I beleive this
      will be necessary (or at least good) when "multiple timezones in the
      same query" is eventually implemented. And code-wise, this was the time
      to do it.
      
      
      There are no user-visible changes at this time. Implementing the
      "multiple zones in one query" is a later step...
      
      This also gets rid of some of the cruft needed to "back out a timezone
      change", since we previously couldn't check a timezone unless it was
      activated first.
      
      Passes regression tests on win32, linux (slackware 10) and solaris x86.
      
      Magnus Hagander
      aa8bdab2
      History
      Attached patch gets rid of the global timezone in the following steps:
      Bruce Momjian authored
      * Changes the APIs to the timezone functions to take a pg_tz pointer as
      an argument, representing the timezone to use for the selected
      operation.
      
      * Adds a global_timezone variable that represents the current timezone
      in the backend as set by SET TIMEZONE (or guc, or env, etc).
      
      * Implements a hash-table cache of loaded tables, so we don't have to
      read and parse the TZ file everytime we change a timezone. While not
      necesasry now (we don't change timezones very often), I beleive this
      will be necessary (or at least good) when "multiple timezones in the
      same query" is eventually implemented. And code-wise, this was the time
      to do it.
      
      
      There are no user-visible changes at this time. Implementing the
      "multiple zones in one query" is a later step...
      
      This also gets rid of some of the cruft needed to "back out a timezone
      change", since we previously couldn't check a timezone unless it was
      activated first.
      
      Passes regression tests on win32, linux (slackware 10) and solaris x86.
      
      Magnus Hagander