Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
5763683c
Commit
5763683c
authored
26 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
On reflection, filesize limit ought to be an exact power
of 2 to save a few cycles in md.c. So, make it 2^30 not 10^9.
parent
5ce851dc
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/include/config.h.in
+7
-6
7 additions, 6 deletions
src/include/config.h.in
with
7 additions
and
6 deletions
src/include/config.h.in
+
7
−
6
View file @
5763683c
...
...
@@ -32,17 +32,18 @@
* Thus, the maximum size of a single file is RELSEG_SIZE * BLCKSZ;
* relations bigger than that are divided into multiple files.
*
* CAUTION: RELSEG_SIZE * BLCKSZ must be less than your OS' limit on file
size.
* This is typically 2Gb or 4Gb in a 32-bit operating system. By
default,
* we make the limit
one billion bytes
to avoid any possible integer-overflow
* CAUTION: RELSEG_SIZE * BLCKSZ must be less than your OS' limit on file
*
size.
This is typically 2Gb or 4Gb in a 32-bit operating system. By
*
default,
we make the limit
1Gb
to avoid any possible integer-overflow
* problems within the OS. A limit smaller than necessary only means we
* divide a large relation into more chunks than necessary, so it seems best
* to err in the direction of a small limit.
* divide a large relation into more chunks than necessary, so it seems
* best to err in the direction of a small limit. (Besides, a power-of-2
* value saves a few cycles in md.c.)
*
* CAUTION: you had best do an initdb if you change either BLCKSZ or
* RELSEG_SIZE.
*/
#define RELSEG_SIZE (
100
0000000 / BLCKSZ)
#define RELSEG_SIZE (
0x4
0000000 / BLCKSZ)
/*
* The following is set using configure.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment