This is a discussion on pgsql: >> Do you agree that using a hashtable for it in general is a within the pgsql Committers forums, part of the PostgreSQL category; --> Log Message: ----------- >> Do you agree that using a hashtable for it in general is a good idea ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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/cvsw...1=1.32&r2=1.33) ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) |
| Thread Tools | |
| Display Modes | |
|
|