From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)bowt(dot)ie> |
Subject: | allow segment size to be set to < 1GiB |
Date: | 2022-11-07 17:13:55 |
Message-ID: | 20221107171355.c23fzwanfzq2pmgt@awork3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I was recently reminded of my previous desire to allow setting the segment
size to less than 1GB. It's pretty painful to test large amount of segments
with a segment size of 1GB, certainly our regression test don't cover anything
with multiple segments.
This likely wouldn't have detected the issue fixed in 0e758ae89a2, but it make
it easier to validate that the fix doesn't break anything badly.
In the attached patch I renamed --with-segsize= to --with-segsize-mb= /
-Dsegsize= to -Dsegsize_mb=, to avoid somebody building with --with-segsize=2
or such suddenly ending up with an incompatible build.
Greetings,
Andres Freund
Attachment | Content-Type | Size |
---|---|---|
0001-allow-smaller-segsize.patch | text/x-diff | 8.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ronan Dunklau | 2022-11-07 17:30:16 | Re: Add proper planner support for ORDER BY / DISTINCT aggregates |
Previous Message | Pavel Luzanov | 2022-11-07 16:58:50 | Re: Add proper planner support for ORDER BY / DISTINCT aggregates |