aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/spgist/spginsert.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2013-11-01 12:51:27 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2013-11-01 12:51:27 -0400
commit1c8a7f617fd1d38cb0540266e4fca6835f61005a (patch)
tree1b9ac91d386ba2103ff94872303506b8f038ede0 /src/backend/access/spgist/spginsert.c
parent631dc390f49909a5c8ebd6002cfb2bcee5415a9d (diff)
downloadpostgresql-1c8a7f617fd1d38cb0540266e4fca6835f61005a.tar.gz
postgresql-1c8a7f617fd1d38cb0540266e4fca6835f61005a.zip
Remove internal uses of CTimeZone/HasCTZSet.
The only remaining places where we actually look at CTimeZone/HasCTZSet are abstime2tm() and timestamp2tm(). Now that session_timezone is always valid, we can remove these special cases. The caller-visible impact of this is that these functions now always return a valid zone abbreviation if requested, whereas before they'd return a NULL pointer if a brute-force timezone was in use. In the existing code, the only place I can find that changes behavior is to_char(), whose TZ format code will now print something useful rather than nothing for such zones. (In the places where the returned zone abbreviation is passed to EncodeDateTime, the lack of visible change is because we've chosen the abbreviation used for these zones to match what EncodeTimezone would have printed.) It's likely that there is now a fair amount of removable dead code around the call sites, namely anything that's meant to cope with getting a NULL timezone abbreviation, but I've not made an effort to root that out. This could be back-patched if we decide we'd like to fix to_char()'s behavior in the back branches, but there doesn't seem to be much enthusiasm for that at present.
Diffstat (limited to 'src/backend/access/spgist/spginsert.c')
0 files changed, 0 insertions, 0 deletions