aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/timestamp.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-06-15 00:09:26 +0000
committerBruce Momjian <bruce@momjian.us>2005-06-15 00:09:26 +0000
commitf4c4f1ce52b53d61bd000e2f113f352f8a52d8c2 (patch)
treea8e3ff3c7aff44cf87c6d6822509fd0d72a072b0 /src/backend/utils/adt/timestamp.c
parentb4132fd0acd506ff62404edb8f9296dfaa8a4427 (diff)
downloadpostgresql-f4c4f1ce52b53d61bd000e2f113f352f8a52d8c2.tar.gz
postgresql-f4c4f1ce52b53d61bd000e2f113f352f8a52d8c2.zip
>> Do you agree that using a hashtable for it in general is a good idea
>> assuming this sideeffect is removed, though? > >I have no problem with the hashtable, only with preloading it with >everything. What I'd like to see is that the table inherited at fork() >contains just the data for the default timezone. (At least in the >normal case where that setting hasn't been changed since postmaster >start.) Here's a patch doing this. Changes score_timezone not to use pg_tzset(), and thus not loading all the zones in the cache. The actual timezone being picked will be set using set_global_timezone() which in turn calls pg_tzset() and loads it in the cache. Magnus Hagander
Diffstat (limited to 'src/backend/utils/adt/timestamp.c')
0 files changed, 0 insertions, 0 deletions