user/sven/postgresql.git

Age	Commit message (Collapse)	Author
2006-07-14	Remove 576 references of include files that were not needed.	Bruce Momjian

2006-07-14	Revert part of recent include patch not ready for application.	Bruce Momjian

2006-07-14	Add additional includes needed on some platforms.	Bruce Momjian

2005-10-15	Standard pgindent run for 8.1.	Bruce Momjian

2005-06-20	Cosmetic improvements to the timezone code: remove the use of the	Neil Conway
	'register' qualifier, make some function declarations more consistent, and so on.
2005-04-19	Attached patch gets rid of the global timezone in the following steps:	Bruce Momjian
	* 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
2004-08-29	Pgindent run for 8.0.	Bruce Momjian

2004-06-03	Adjust our timezone library to use pg_time_t (typedef'd as int64) in	Tom Lane
	place of time_t, as per prior discussion. The behavior does not change on machines without a 64-bit-int type, but on machines with one, which is most, we are rid of the bizarre boundary behavior at the edges of the 32-bit-time_t range (1901 and 2038). The system will now treat times over the full supported timestamp range as being in your local time zone. It may seem a little bizarre to consider that times in 4000 BC are PST or EST, but this is surely at least as reasonable as propagating Gregorian calendar rules back that far. I did not modify the format of the zic timezone database files, which means that for the moment the system will not know about daylight-savings periods outside the range 1901-2038. Given the way the files are set up, it's not a simple decision like 'widen to 64 bits'; we have to actually think about the range of years that need to be supported. We should probably inquire what the plans of the upstream zic people are before making any decisions of our own.
2004-05-21	pgindent did a pretty awful job on the timezone code, particularly with	Tom Lane
	respect to doubly-starred comment blocks. Do some manual cleanup.
2004-05-21	Pgindent timezone file, per request from Tom.	Bruce Momjian

2004-05-21	Integrate src/timezone library for all platforms. There is more we can	Tom Lane
	and should do now that we control our own destiny for timezone handling, but this commit gets the bulk of the picayune diffs in place. Magnus Hagander and Tom Lane.