pgsql: >> Do you agree that using a hashtable for it in general is a

Поиск
Список
Период
Сортировка
От momjian@svr1.postgresql.org (Bruce Momjian)
Тема pgsql: >> Do you agree that using a hashtable for it in general is a
Дата
Msg-id 20050615000927.30FFD528CE@svr1.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Log Message:
-----------
>> 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

Modified Files:
--------------
    pgsql/src/timezone:
        pgtz.c (r1.32 -> r1.33)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/pgtz.c.diff?r1=1.32&r2=1.33)

В списке pgsql-committers по дате отправления:

Предыдущее
От: momjian@svr1.postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Now \d show tablespace of indices per discussion.
Следующее
От: momjian@svr1.postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Support 3 and 4-byte unicode characters.