aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvalidate.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-01-31 14:36:56 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2025-01-31 14:36:56 -0500
commitd4c3a6b8ad830882066122081a7141ecd573f45d (patch)
treea007761cdcd4093198d3f2f473da2344e61af261 /src/backend/access/gist/gistvalidate.c
parent041e8b95b8cd251bfec6a3c9c3dd6614de6a4c9b (diff)
downloadpostgresql-d4c3a6b8ad830882066122081a7141ecd573f45d.tar.gz
postgresql-d4c3a6b8ad830882066122081a7141ecd573f45d.zip
Remove obsolete restriction on the range of log_rotation_size.
When syslogger.c was first written, we didn't want to assume that all platforms have 64-bit ftello. But we've been assuming that since v13 (cf commit 799d22461), so let's use that in syslogger.c and allow log_rotation_size to range up to INT_MAX kilobytes. The old code effectively limited log_rotation_size to 2GB regardless of platform. While nobody's complained, that doesn't seem too far away from what might be thought reasonable these days. I noticed this while searching for instances of "1024L" in connection with commit 041e8b95b. These were the last such instances. (We still have instances of L-suffixed literals, but most of them are associated with wait intervals for pg_usleep or similar functions. I don't see any urgent reason to change that.)
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions