mirror of
https://github.com/postgres/postgres.git
synced 2025-08-19 23:22:23 +03:00
Remove CTimeZone/HasCTZSet, root and branch.
These variables no longer have any useful purpose, since there's no reason to special-case brute force timezones now that we have a valid session_timezone setting for them. Remove the variables, and remove the SET/SHOW TIME ZONE code that deals with them. The user-visible impact of this is that SHOW TIME ZONE will now show a POSIX-style zone specification, in the form "<+-offset>-+offset", rather than an interval value when a brute-force zone has been set. While perhaps less intuitive, this is a better definition than before because it's actually possible to give that string back to SET TIME ZONE and get the same behavior, unlike what used to happen. We did not previously mention the angle-bracket syntax when describing POSIX timezone specifications; add some documentation so that people can figure out what these strings do. (There's still quite a lot of undocumented functionality there, but anybody who really cares can go read the POSIX spec to find out about it. In practice most people seem to prefer Olsen-style city names anyway.)
This commit is contained in:
@@ -219,15 +219,6 @@ extern int DateOrder;
|
||||
|
||||
extern int IntervalStyle;
|
||||
|
||||
/*
|
||||
* HasCTZSet is true if user has set timezone as a numeric offset from UTC.
|
||||
* If so, CTimeZone is the timezone offset in seconds (using the Unix-ish
|
||||
* sign convention, ie, positive offset is west of UTC, rather than the
|
||||
* SQL-ish convention that positive is east of UTC).
|
||||
*/
|
||||
extern bool HasCTZSet;
|
||||
extern int CTimeZone;
|
||||
|
||||
#define MAXTZLEN 10 /* max TZ name len, not counting tr. null */
|
||||
|
||||
extern bool enableFsync;
|
||||
|
Reference in New Issue
Block a user