aboutsummaryrefslogtreecommitdiff
path: root/src/backend/storage/file/buffile.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-11-01 13:57:31 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-11-01 13:57:31 -0400
commit45f64f1bbf19283795762df6a54f9aa74fee05f7 (patch)
tree147fc9b2af824f6503f77b0ea2e14d2e7fdd6172 /src/backend/storage/file/buffile.c
parent1c8a7f617fd1d38cb0540266e4fca6835f61005a (diff)
downloadpostgresql-45f64f1bbf19283795762df6a54f9aa74fee05f7.tar.gz
postgresql-45f64f1bbf19283795762df6a54f9aa74fee05f7.zip
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.)
Diffstat (limited to 'src/backend/storage/file/buffile.c')
0 files changed, 0 insertions, 0 deletions